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

Add dwave out to quickquasars #533

Merged
merged 5 commits into from
May 5, 2020
Merged

Add dwave out to quickquasars #533

merged 5 commits into from
May 5, 2020

Conversation

alxogm
Copy link
Contributor

@alxogm alxogm commented May 4, 2020

Their PR is to allow quickquasars to produce mocks with pixels width specified by the user. This is related to the more general issue raised by Andreu #532.

Change is very simple, I've tested it in a small run here /global/cfs/projectdirs/desi/mocks/lya_forest/develop/london/qq_desi/v9.0/v9.0.0/desi-1.2-1.tmp/

I was waiting for some feedback from the DLA team, but I think it will be fine if we just go ahead.

**Other changes are only some missing spaces I added ...

@alxogm alxogm requested a review from andreufont May 4, 2020 04:30
@@ -299,6 +301,11 @@ def simulate_one_healpix(ifilename,args,model,obsconditions,decam_and_wise_filte
log.info("Creating dir {}".format(pixdir))
os.makedirs(pixdir)

if not eboss is None:
dwave_out=1. #to keep the same value used for DR16
Copy link
Contributor

Choose a reason for hiding this comment

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

@alxogm - I'm worried that eBOSS users might think that dwave_out will also affect them, and here we hide its effect. We could rename the adgument to dwave_DESI, or at least edit the help string to make it clear it only affects DESI. May be add also a print warning here if you were trying to run with eBOSS and also trying to change the value of dwave_out?

Copy link
Contributor

Choose a reason for hiding this comment

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

Actually, the eBOSS version should really just ignore dwave_out, since the SDSS spectrograph doesn't have constant pixels in wavelength, but logarithmic.

I'd suggest to set dwave_out=None when running with eBOSS flag.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi @andreufont, right!

dwave_out=None was my first option, but I changed to 1 because I was not considering the there is an eBOSS branch that is not yet merged, so I didn't see what you mention about eBOSS not having constant pixels. So I've set it back to dwave_out=None, and changed the argument name also, to avoid confusion...

@@ -102,7 +104,7 @@ def parse(options=None):

parser.add_argument('--mags', action = "store_true", help="DEPRECATED; use --bbflux")

parser.add_argument('--bbflux', action = "store_true", help="compute and write the QSO broad-band fluxes in the fibermap")
parser.add_argument('--bbflux', type=bool, default=True, help="compute and write the QSO broad-band fluxes in the fibermap ")
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ups! I think I accidentally pushed an unrelated change... should I included in this PR or left it aside?

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm ok putting it all together, it is a small fix.

@@ -102,7 +104,7 @@ def parse(options=None):

parser.add_argument('--mags', action = "store_true", help="DEPRECATED; use --bbflux")

parser.add_argument('--bbflux', action = "store_true", help="compute and write the QSO broad-band fluxes in the fibermap")
parser.add_argument('--bbflux', type=bool, default=True, help="compute and write the QSO broad-band fluxes in the fibermap ")
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm ok putting it all together, it is a small fix.

@alxogm
Copy link
Contributor Author

alxogm commented May 5, 2020

@andreufont I made a few more changes to handle the --bblux as default, previous syntax was not correct... I don't see when we will need it to set it as False but I better left the option anyway. I included an update of the warning message of a deprecated argument, just in case... I'll merge if there are no more changes. Thanks

Copy link
Contributor

@andreufont andreufont left a comment

Choose a reason for hiding this comment

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

Are you sure we need to options for bbflux, one to set it to true, and one to set it to false? I think this is really confusing, and unnecessary for an option that we really don't expect people to use.

@alxogm
Copy link
Contributor Author

alxogm commented May 5, 2020

We decided to do a clean up of arguments in a separate PR. Then I'll merge once tests passes.

Copy link
Contributor

@andreufont andreufont left a comment

Choose a reason for hiding this comment

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

great

@weaverba137
Copy link
Member

Can the branch add_dwave_out be deleted?

@alxogm alxogm deleted the add_dwave_out branch January 20, 2021 23:42
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.

3 participants