Skip to content
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

consider using a parameterized project_code to target the same ProjectParameters_ file in workflow.transition.monitor as the intended target #79

Closed
cjyetman opened this issue Feb 27, 2024 · 1 comment · Fixed by #81

Comments

@cjyetman
Copy link
Member

It would be advantageous if a user could specify a project_code so that it could target the same ProjectParameters_[INITIATIVE].yml in workflow.transition.monitor as the one which the benchmarks are intended for.

e.g. when creating the config file here

project_code = investor_name,

This would remove the necessity of managing a separate config file in workflow.transition.monitor specifically for indices, e.g. here, and ensure that the same configuration of PACTA analysis is used for the specified quarter/initiative.

AlexAxthelm added a commit that referenced this issue Feb 27, 2024
Allow specifying a project code in config, to not need to maintain separate indices parameter files

Closes: #79
@jdhoffa
Copy link
Member

jdhoffa commented Feb 27, 2024

I back this!

AlexAxthelm added a commit that referenced this issue Feb 27, 2024
Allow specifying a project code in config, to not need to maintain separate indices parameter files

Closes: #79
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 a pull request may close this issue.

2 participants