-
Notifications
You must be signed in to change notification settings - Fork 22
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
Update to new specsim v0.3 API #80
Comments
I am using the output generated by the following command, with specsim v0.2 installed, as my baseline for working on this issue:
Note that DESI_BASIS_TEMPLATES and DESISIM must be set appropriately. This generates some warnings which I will ignore:
|
This is the old filter code complaining (since the desisim branch I've been developing which uses speclite.filters) has not yet been merged. However, this code is also producing non-catastrophic warnings which I've decided to not yet suppress while we're still vetting & testing these ~major changes. |
Using branch
There are now some new warnings from astropy (via specsim) but these are a separate issue (deishub/desimodel#4):
I am declaring success with quickbrick and moving on to quickgen now. |
I am using the output generated by the following command, with specsim v0.2 installed, as my baseline for updating quickgen:
The simspec and fibermap files are taken from #57. Note that DESI_BASIS_TEMPLATES, DESISIM and DESI_SPECTRO_REDUX must be set appropriately. The output is:
|
Using branch
|
I am in the middle of some substantial changes to specsim that move all of the hardcoded desimodel dependencies into a yaml configuration file, with some unavoidable API changes. These changes lay the groundwork for simulating other instruments (eBOSS, for example) and also running Travis tests without desimodel.
This issue is to update desisim's usage of specsim when v0.3 is released with the new API. I believe that the only affected code is
bin/quickgen
andbin/quickbrick
. A version requirementspecsim >= 0.3
will also need to be imposed, but I'm not sure how to do that (it looks likespecsim
is not mentioned at all in the currentrequirements.txt
).The text was updated successfully, but these errors were encountered: