You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I talked to @moustakas with respect to #608 and the suggestion is to separate populating maskbits from within select mock targets and instead pre-burn maskbits files for the mock targets by rescoping the select_randoms script to read in a set of mock (ra, dec) and continue from those, rather than from a set of Poisson points, when flagged appropriately.
Few points:
-- We're going to have 1000s of mocks to have to do a mask calculation for, for each tracer, so speed
is important.
-- We'll also have the use case where we want to save depths, etc. rather, than just an in/out flag for
a given tracer. Note that the in/out decision will still require NOBS etc, i.e. it'll call is_in_elg_mask.
-- It might be better to simply 'sphere match' to the random catalogue? I've heard arguments both ways.
There's a cosmosim call on Thursday likely addressing some of these issues. Putting this out there before I try anything again.
The text was updated successfully, but these errors were encountered:
I talked to @moustakas with respect to #608 and the suggestion is to separate populating maskbits from within select mock targets and instead pre-burn maskbits files for the mock targets by rescoping the select_randoms script to read in a set of mock (ra, dec) and continue from those, rather than from a set of Poisson points, when flagged appropriately.
Few points:
-- We're going to have 1000s of mocks to have to do a mask calculation for, for each tracer, so speed
is important.
-- We'll also have the use case where we want to save depths, etc. rather, than just an in/out flag for
a given tracer. Note that the in/out decision will still require NOBS etc, i.e. it'll call is_in_elg_mask.
-- It might be better to simply 'sphere match' to the random catalogue? I've heard arguments both ways.
There's a cosmosim call on Thursday likely addressing some of these issues. Putting this out there before I try anything again.
The text was updated successfully, but these errors were encountered: