Sandro Dias Pinto Vitenti
Sandro Dias Pinto Vitenti
My problem here is that by default CosmoMC and MontyPython will give different results for what people expect to be the same likelihood+priors (unless this parameter does not correlate with...
The object structure is fine. The name can be `GalaxySDPosition` that is instead of `GalaxySampleDistribution` or `GSD` we can use `GalaxySD`. What do you think?
Done in #165
See https://osqp.org/ too
We should create a doc file containing the parameters' bounds and the references where we got them.
The support for this was already implemented, however, these values are not being included in the output catalog.
Hi @tilmantroester , we have been working on the redesign of two point in the last two meetings and we are using your work here as a source of ideas...
It seems that all proposed features are already implemented. Please open another issue if you find there is something missing.
This is already supported by NumCosmo's connector. Moreover, in Augur you can find code to do that, see for example [srd_y1_3x2_like.py](https://github.com/LSSTDESC/augur/blob/master/examples/srd_y1_3x2_like.py), where they generate a data vector from a theory...
The CosmoSIS connector presently includes a section in the DataBlock labeled data_vector. This section contains three elements: `firecrown_theory` (the theory vector), `firecrown_data` (the data vector), and `firecrown_inverse_covariance` (the inverse covariance)....