Open jchiang87 opened 6 years ago
Yes. I suppose we should protect against A_v == NaN
the same way we did with R_v
. Let me check to see if this is a bug in the underlying catalog, or something sims_GCRCatSimInterface
is introducing.
I can confirm that, in protoDC2 v3, the galaxy with galaxy_id = 4121104
has A_v_disk = R_v_disk = nan
, but stellar_mass_disk > 0
.
@evevkovacs @abensonca
@jchiang87 I will issue a PR against sims_GCRCatSimInterface to protect against this
@danielsf @yymao Using
v0.2.0
, I'm seeingnan
values appearing in the extinction entries for galaxies. Here's a grep of the gunzipped (and renamed) galaxy catalog that I generated for Run1.2p visit 197356:This is for a full focalplane fov (~2.1 deg radius), so these are fairly rare, but they are causing
imsim
/galsim
to crash when computing the flux for these entries. There is protection against nan values for theR_v
entries here. Should we do something similar for theA_v
values too?