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

What is the intended use of technosphereflows.py? #249

Open
dt-woods opened this issue Aug 13, 2024 · 2 comments
Open

What is the intended use of technosphereflows.py? #249

dt-woods opened this issue Aug 13, 2024 · 2 comments
Labels
in v2 Issues marked for inclusion in version 2 question

Comments

@dt-woods
Copy link
Collaborator

@m-jamieson, do you know how technosphereflows.py is meant to be used?

I see that the parameter, "fuel_name_file" is pulled from the configuration file to create the CSV file path to "fuelname.csv" or "fuelname_1.csv" and that this CSV file is read by map_heat_inputs_to_fuel_names method in technosphereflows.py; however, I don't see any modules that call or import this method.

Is there a post-process that this serves?

@m-jamieson
Copy link
Collaborator

Not to completely shirk my responsibilities here, but blame tells me I had nothing to do with it! The original commit states:
New file to handle mapping of technosphere input flows before writing…
… the generation dictionary (just handles fuels for now)

It also looks to me like it's not used anywhere, so I'm okay with removing it. I wouldn't have called it from any external routines. And the fuel inputs to the various processes are now handled in other modules.

@dt-woods
Copy link
Collaborator Author

I'll handle appropriately. Thanks, Matt!

dt-woods added a commit to KeyLogicLCA/ElectricityLCI that referenced this issue Aug 13, 2024
@dt-woods dt-woods added the in v2 Issues marked for inclusion in version 2 label Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in v2 Issues marked for inclusion in version 2 question
Projects
None yet
Development

No branches or pull requests

2 participants