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

Extended Source Response Generation #267

Closed
hiyoneda opened this issue Nov 19, 2024 · 0 comments · Fixed by #284
Closed

Extended Source Response Generation #267

hiyoneda opened this issue Nov 19, 2024 · 0 comments · Fixed by #284
Assignees

Comments

@hiyoneda
Copy link
Contributor

I made schematics about how the classes related to the response matrix are connected through their class methods.
For the point source response, FullDetectorResponse is tied with PointSourceResponse by FullDetectorResponse.get_point_source_response, and the expected counts are calculated through PointSourceResponse.get_expectation.

When I implemented ExtendedSourceResponse, I was focusing on the expected count calculation part, i.e., ExtendedSourceResponse.get_expection and ExtendedSourceResponse.get_expectation_from_astromodel. So, currently, there is no function to generate ExtendedSourceResponse from FullDetectorResponse.

We can discuss where we should add such a method in cosipy, but I think it is natural to add a new method in FullDetectorResponse.
It can be based on some notebooks on which we generated the pre-computed response file for DC2 (while I don't know where the latest one is (and who has it)).

Regarding this, I have two questions.

  • SpacecraftFile also has a method to generate PointSourceResponse; SpacecraftFile.get_psr_rsp. Do you think we should keep it or remove it in the future?
  • Do you think that we should rename ExtendedSourceResponse.get_expection to something like ExtendedSourceResponse.get_expection_from_hist and ExtendedSourceResponse.get_expectation_from_astromodel to ExtendedSourceResponse.get_expection? It is because the input of PointSourceResponse.get_expectation is astromodel function, but that of ``ExtendedSourceResponse.get_expection` is the model cube histogram. The naming is the same, but the input parameter is different, which may be confusing?

extended_response_generation 001

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants