As discussed recently on the DESI Slack, the current method can cause correlations between mocks if the users provide consecutive seeds to generate different realizations.
It would be great to modify the code to avoid this potential problem, and we have already discussed a few possible implementations with @mruizherrerab .
As discussed recently on the DESI Slack, the current method can cause correlations between mocks if the users provide consecutive seeds to generate different realizations.
It would be great to modify the code to avoid this potential problem, and we have already discussed a few possible implementations with @mruizherrerab .