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

to do: add directory locations for LiAISON to CELAVI files #220

Open
4 tasks done
rjhanes opened this issue Jan 17, 2025 · 2 comments
Open
4 tasks done

to do: add directory locations for LiAISON to CELAVI files #220

rjhanes opened this issue Jan 17, 2025 · 2 comments
Assignees

Comments

@rjhanes
Copy link
Collaborator

rjhanes commented Jan 17, 2025

Updates being made in dev-circfutures_liaison branch.

TJ to update the PylcaCelavi class definition, update the instantiation in scenario.py, remove extraneous parameters from YAML file(s), THEN we proceed

  • casestudy.yaml: add these

liaison_reeds_project_name='USMid_Case'
liaison_reeds_database='premise_base'
celavi_lca_project='USMid_Case_celavi'

  • the outer repo of the data folder - add as a parameter to the PylcaCelavi instantiation, line 317 or thereabouts in scenario.py
  • To add on the liaison side: have hard coded the inputs/liaison and generated/liaison locations within the outer data folder
  • automatically create the liaison subdirectory w/in generated if does not exist
@rjhanes rjhanes changed the title to do: add directories for LiAISON to CELAVI files to do: add directory locations for LiAISON to CELAVI files Jan 17, 2025
@rjhanes
Copy link
Collaborator Author

rjhanes commented Jan 21, 2025

Adding a liaison_params input parameter (dictionary) to PylcaCelavi class with this structure:

{'liaison_reeds_project_name': 'USMid_Case', 'liaison_reeds_database': 'premise_base', 'celavi_lca_project': 'USMid_Case_celavi'}

rjhanes added a commit that referenced this issue Jan 21, 2025
@rjhanes
Copy link
Collaborator Author

rjhanes commented Jan 21, 2025

@tjlca Please test when you have time and LMK if any adjustments need to be made. I've verified that the paths are being constructed correctly and the liaison_params dict has the contents from the initial comment above.

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

No branches or pull requests

2 participants