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
During a discussion on slack with Dr. Shajib we talked about the possibility of implementing a function to obtain the MCMC posterior of the amplitude parameters for the light profiles, as it wasn't directly stored to save memory and avoid modifying the original dimension of the MCMC chain. This would be best to be done as an "a posteriori" tool, which can be called only when needed. I am eager to implement it myself, but being new to the program, any help would be greatly appreciated!
The text was updated successfully, but these errors were encountered:
Thank you very much @GiacomoQueirolo for opening this issue!
If you have an idea and a wage way of implementing, you can start a pull request even if it is in very skeleton version. Check out the developer page for how to do it: https://lenstronomy.readthedocs.io/en/latest/contributing.html
Also note, that for many samplers, the chains are directly being handled and stored by the package (such as emcee etc) and you could also look in their documentation of how to potentially add other meta data to the chains.
During a discussion on slack with Dr. Shajib we talked about the possibility of implementing a function to obtain the MCMC posterior of the amplitude parameters for the light profiles, as it wasn't directly stored to save memory and avoid modifying the original dimension of the MCMC chain. This would be best to be done as an "a posteriori" tool, which can be called only when needed. I am eager to implement it myself, but being new to the program, any help would be greatly appreciated!
The text was updated successfully, but these errors were encountered: