Skip to content

Ngmixv2 version #141

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 42 commits into
base: process-real
Choose a base branch
from
Open

Ngmixv2 version #141

wants to merge 42 commits into from

Conversation

GeorgeVassilakis
Copy link
Collaborator

Creating a pull request just to compare the version of metacalibration in the ngmixv2 branch versus process-real branch. Theoretically, the ngmixv2 branch was a complete working pipeline with ngmix v2.0.0 but was merged into master and got forgotten about (@sweverett can you confirm this?). If so, we want to integrate ngmixv2 into the new pipeline.

sweverett and others added 30 commits July 25, 2022 11:41
…` for our module metacal running. Also generalied `LogPrint` to handle the case of no log
* Finished implementing ubserseg weight creation in metacal fitting. Closes #77

* Added env files for both versions of `ngmix`

* fixed env file name

* Added some missing optional fields to pipeline modules
…ore stringent in range than the other modules.
@GeorgeVassilakis GeorgeVassilakis self-assigned this Aug 9, 2024
@sweverett
Copy link
Collaborator

Hello! It's been ages, but here's my memory of the situation:

  1. I made the ngmixv2 branch to provide classes & utilities to interface with more modern versions of ngmix that had API-breaking changes (hence the v2.X bit)
  2. I tested the classes and had a working version that ran the newer ngmix. As they had different dependencies, we had two separate conda env files
  3. @mcclearyj and my work bifurcated at some point where she focused on finishing the lensing in the blue paper (w/ ngmix v1.X I believe) while I built OBA. At that time I stopped focusing on any compatibility with the existing repo
  4. I went on leave and never touched this again. I have no memory of whether the branch was ever merged into main

Hopefully that helps!

@GeorgeVassilakis
Copy link
Collaborator Author

Great, thank you for that update, Spencer! That is really helpful. We weren't sure whether the ngmixv2 branch was an operational version or not (at the time of your last commit), so thank you for confirming that it worked when you worked on it. I plan on trying to pull the pieces together of this ngmixv2 branch and get this merged into our process-real branch, which is what we've been working on for the last 1+ year. Appreciate the help!

@sweverett
Copy link
Collaborator

Good luck! Feel free to ask any questions that you run into

@GeorgeVassilakis
Copy link
Collaborator Author

Thanks, will do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants