Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify monitor and detector handling guidelines #6

Merged
merged 2 commits into from
Mar 4, 2024

Conversation

SimonHeybrock
Copy link
Member

In this case I updated some guidelines IDs, which we should generally avoid. As this was just merged this morning and is not implemented anywhere I think this should be ok.

- Avoids loading large data into memory that is not needed for the reduction.
- Avoids keeping large data alive in memory if output metadata extraction depends on auxiliary input data or input metadata.
Monitor data can be extremely large when operating in event mode.
Loading only individual monitors avoids loading unnecessary data and allows for more efficient parallelism and reduction in memory use.
Copy link
Member

Choose a reason for hiding this comment

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

Not really related to guidelines, but what about transforms? Are there cases where we need to load more than just a monitor in order to find the position? Same for detectors.

Copy link
Member Author

Choose a reason for hiding this comment

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

This can be handled by the loader. We should probably put this into ESSreduce (or even ScippNexus), and just wrap that elsewhere.

Copy link
Member

Choose a reason for hiding this comment

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

That means reimplementing the logic to walk depends-on chains. So it seems to be something that should be handled by compute_positions or a similar function in ScippNexus.

@SimonHeybrock SimonHeybrock merged commit 60bcb06 into main Mar 4, 2024
3 checks passed
@SimonHeybrock SimonHeybrock deleted the guidelines-update branch March 4, 2024 03:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants