Skip to content

fix: adapt Mat_map_surface_plot_dist and Mat_map_surface_plot_dist to the new surface type and range lookup#5359

Merged
kodiakhq[bot] merged 2 commits intoacts-project:mainfrom
veprbl:pr/fix_dist_and_1D_macro
Apr 17, 2026
Merged

fix: adapt Mat_map_surface_plot_dist and Mat_map_surface_plot_dist to the new surface type and range lookup#5359
kodiakhq[bot] merged 2 commits intoacts-project:mainfrom
veprbl:pr/fix_dist_and_1D_macro

Conversation

@veprbl
Copy link
Copy Markdown
Contributor

@veprbl veprbl commented Apr 16, 2026

This is a minor sequel to
#4931
and
#5046

The goal is to fill some missing code in the two remaining macros.

--- END COMMIT MESSAGE ---

@github-actions github-actions bot added this to the next milestone Apr 16, 2026
@github-actions github-actions bot added the Component - Examples Affects the Examples module label Apr 16, 2026
@veprbl
Copy link
Copy Markdown
Contributor Author

veprbl commented Apr 16, 2026

This was tested at ePIC eic/epic#1076 (comment)

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 16, 2026

📊: Physics performance monitoring for 18f4ebf

Full contents

physmon summary

Copy link
Copy Markdown
Contributor

@andiwand andiwand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fine by me

I fear these scripts are bound to break as they are not monitored or maintained. if they are useful to you I am happy to update them. looking a bit further out we should either test them, migrate them to python, or completely drop them and you can pull them into your repo, in case this is even possible due to internal dependencies

@sonarqubecloud
Copy link
Copy Markdown

@kodiakhq kodiakhq bot merged commit 0f3e349 into acts-project:main Apr 17, 2026
42 checks passed
@veprbl veprbl deleted the pr/fix_dist_and_1D_macro branch April 17, 2026 12:51
@veprbl
Copy link
Copy Markdown
Contributor Author

veprbl commented Apr 17, 2026

@andiwand I agree, the support model is less than perfect, but I'd like them to be corrected best effort at least. These scripts are in an awkward spot because they support surface material maps only. If we build a testing infrastructure on the Acts' side now, it will add some more work to do during the transition to 3rd gen and python?

@andiwand
Copy link
Copy Markdown
Contributor

I think material mapping validation will be the same between gen1 and gen3? @paulgessinger @noemina know more about this

so in case you have some spare cycles we could either have some testing around the current scripts or port them to python if it is possible without making it terribly slow and monitor that. for example by scanning an eta-phi wedge of ODD and having some reference plots we compare to

@andiwand andiwand modified the milestones: next, v46.4.0, v46.3.0 Apr 18, 2026
paradajzblond pushed a commit to paradajzblond/acts that referenced this pull request Apr 20, 2026
… the new surface type and range lookup (acts-project#5359)

This is a minor sequel to
acts-project#4931
and
acts-project#5046

The goal is to fill some missing code in the two remaining macros.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Component - Examples Affects the Examples module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants