Closed evevkovacs closed 11 months ago
@evevkovacs thanks.
Two questions:
The understanding has been that everything with a config file in the master branch is kept in the shared area. For one thing, this makes it easy to maintain the catalogs at another installation. Is there a reason not to copy the data there in this case?
I will copy to the shared directory (if I can, or ping Heather) and update the configuration file. The diffsky catalogs are evolving rapidly, so this one will soon become obsolete, but that happened with cosmoDC2 also.
Oops, I forgot that I had made those edits in the reader. I will have to edit those and make a version check or do something similar to ensure that I am not breaking the reader for the earlier catalogs. When perlmutter comes back up I will make those changes, test and push the new version.
@yymao Here is the updated PR for the roman-rubin reader. I copied the latest catalog to the shared area, deleted the previous obsolete versions and updated the cosmodc2 reader so that it works on the new catalog and is backwards compatible.
@evevkovacs -- are you planning to remove the configs that have files not in the shared space?
Two catalog configuration files for test catalogs for the roman-desc sims. The diffsky catalog is stored in the CS directory. It is not critical for this catalog to be generally available, but the special named version of the cosmoDC2 catalog should be pushed up to the main branch for more general use cosmodc2.py has also been modified for the diffsky catalog and this should also go in the main branch.