Empty psfMagErr in objectForcedSource for DP2

Hi folks!

I’m currently using the object catalog in EDP2, particularly the light curves in objectForcedSource. I’m a bit confused because some objects have ~40 epochs in their light curves, with ~30 filled psfMag values, but most of the points have an empty/NaN psfMagErr. For example, objectId: 756398235370674612 has 44 epochs in its light curve, 24 of the psfMag values are null, and 40 of the psfMagErr values are null. None of these observations are flagged, so I was wondering what this means — are these observations still reliable? Thank you!

Hi @scharney, thanks for the question. I was unable to reproduce the issue. In the FourcedSource DP2 catalog for objectId= 756398235370674612, I see 46 measurements with no null entries for psfFlux or psfFluxErr using the Portal ADQL query:
SELECT objectId,visit,detector,band,psfFlux,psfFluxErr,psfDiffFlux,psfDiffFluxErr
FROM dp2.ForcedSource
WHERE (objectId =756398235370674612).

Can you provide either the portal ADQL query or code you used that resulted in the null entries?

NULLs are probably resulting from attempted conversion of all the negative fluxes here to magnitude?