-
Notifications
You must be signed in to change notification settings - Fork 54
MeVPrtl LLP (fcls and files) #844
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
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove from commit to avoid ROOT files in the repository
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove from commit to avoid ROOT files in the repository
|
|
||
|
|
||
| #DECAY CONFIGS | ||
| decay_llp: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add a comment stating that the decay part is still work in progress and is not meant to be used (I see there are a lot of HNL-specific parameters there).
|
@SabrinaBrickner Could you respond to some of these follow up q's? |
|
For the record, this is an ongoing review and it is not required to converge for the Fall Production. @GaetanoFricano is also working on this. |
|
Just checking in on this. Any updates? |
Description
Adds 5 files to the MevPrtl generator. 3 of these files are the fcls needed to run the new set of LLP modules, and the other 2 files contain the output of running the fcls with the new LLP tools.
Checklist
Reviewers,AssigneesDevelopementRelevant PR links (optional)
Does this PR require merging another PR in a different repository (such as sbnanobj/sbnobj etc.)?
Yes -> in sbncode it requires "MeVPrtl LLP (tools)"
Link(s) to docdb describing changes (optional)
Is there a docdb describing the issue this solves or the feature added?