I'm planning to separate out the photo-z posterior forward model functionality from chippr, at the request of TJP, into something that would be callable by CLMM's mock_data.py in the foreseeable future. (It may be copied out directly now, but this should probably wait until after v1.0.)
Of course CL-specific aspects of mock data generation could continue to develop in CLMM or other CL tools, but we should try to leverage other DESC codes as much as possible, i.e. use XWG resources whenever possible. In particular, some of this functionality is in-scope for TJP plans. (Tagging @elisachisari as a reminder to follow up about separating out the PZxTJP modeling code.)
This is part of a bigger conceptual change for mock_data to perhaps move from a support module to a part of clmm proper for the sake of forward-modeling that could be part of an inference, to be tackled after v1.0.
I'm planning to separate out the photo-z posterior forward model functionality from chippr, at the request of TJP, into something that would be callable by CLMM's mock_data.py in the foreseeable future. (It may be copied out directly now, but this should probably wait until after v1.0.)
Of course CL-specific aspects of mock data generation could continue to develop in CLMM or other CL tools, but we should try to leverage other DESC codes as much as possible, i.e. use XWG resources whenever possible. In particular, some of this functionality is in-scope for TJP plans. (Tagging @elisachisari as a reminder to follow up about separating out the PZxTJP modeling code.)
This is part of a bigger conceptual change for mock_data to perhaps move from a support module to a part of clmm proper for the sake of forward-modeling that could be part of an inference, to be tackled after v1.0.