-
Notifications
You must be signed in to change notification settings - Fork 8
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
M31 Example #2
base: master
Are you sure you want to change the base?
M31 Example #2
Conversation
Very cool! Will take a close look at this in the next few days. |
@cmurray-astro |
Some comments the workflow through step 2 below! Overall it's looking great -- we should probably talk through the comments to fix up a few things. In the meantime:
|
In addition, rather than having the user manually update the datamodel throughout, maybe we can write a function for doing this as needed (similar to the create_datamodel function in Lea's workflow)? |
M31_Example/datamodel.py
Outdated
|
||
# Dust extinction grid definition | ||
extLaw = extinction.Generalized_RvFALaw( | ||
ALaw=extinction.Generalized_DustExt(curve="F20"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
F20 needs to be changed to F19. Newer version of dust_extinction
has the F19 name for this model (paper was published faster than expected).
I found this error in Step 7: create the noise model with our ASTscreate_obsmodel.create_obsmodel( FileNotFoundError: [Errno 2] No such file or directory: 'M31-B09-EAST_chunk.gst.fake_bin2.fits' |
This error is happening because the files in the datamodel.py weren't manually renamed. Look at step 4.5 and 5.5 to see what specific changes need to be made (sorry it's so clunky). We've since then created a function that will automatically rename the variable names in the datamodel.py file but it hasn't been uploaded to the pull request yet. |
Is this PR ready for another review (and possible merging)? |
Almost! There are some minor changes I had to make to update some function keywords, and then the last step where we merge all the files into a
|
Is this an actual error? Looks like a warning. This is the result of a recent PR of mine where I added another extension to the stats file to provide the filter information (useful for the plot_indiv_fit and other scripts). This warning can be removed by changing the line |
It says that it's just a user warning but then the stats.fits file is never outputted. |
I tried changing the function in my code and it still produces the same error.
|
Sounds like more detailed investigation is needed. Probably need look more carefully at the merge_beast_stats.py file. |
When I define the functions in the notebook I'm working in, then the method works. Maybe the change I made in the source files isn't working somehow or being read properly. Would it possible to update the main branch with this fix to see if that will fix my problem? |
A PR is always welcome! |
This is an example workflow for the Beast. It needs the cutout M31 data to run, but that file is larger than 100 MB so let me know if there's a good way for it to run.
The only other thing that's different step-wise is when the datamodel is introduced. For this workflow, it isn't introduced until right before the physics model is created because the datamodel references some files (like the source density map) that isn't normally created until later, making it hard to explain to a new user.