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

timepoints and timeseries #14

Closed
YifanLi86 opened this issue May 5, 2021 · 7 comments
Closed

timepoints and timeseries #14

YifanLi86 opened this issue May 5, 2021 · 7 comments
Assignees

Comments

@YifanLi86
Copy link
Contributor

MORE-DETAILS-TO-BE-POPULATED: temporal profile reduction involved, pending storage + temporal reduction tuning.

Priority: Tier 3
Targeted deadline: July
Goal: develop SWITCH input of profile reduction related inputs, including reduction definition, each time series definition, etc.

@danielolsen
Copy link
Contributor

@YifanLi86 is it fair to say that there are two distinct tasks here? The first task is to somehow determine which representative hour each of our 8760 hours map to (e.g. the file attached in the original post of #46), and the second task is to use this mapping to generate the time-series data that Switch needs to run? I.e. loads.txt, timepoints.txt, timeseries.txt, variable_capacity_factors.txt.

@YifanLi86
Copy link
Contributor Author

@YifanLi86 is it fair to say that there are two distinct tasks here? The first task is to somehow determine which representative hour each of our 8760 hours map to (e.g. the file attached in the original post of #46), and the second task is to use this mapping to generate the time-series data that Switch needs to run? I.e. loads.txt, timepoints.txt, timeseries.txt, variable_capacity_factors.txt.

pretty much, the first task is the output processing which the #46 attachment is for, and the second task is exactly what you described. https://www.dropbox.com/scl/fi/ymt6jg96gy1zut3zx34iu/Action-Items-and-Work-Assignments-05052021.paper?dl=0&rlkey=1dvvru7a7mvdbh7eb6q1ods7e

@danielolsen
Copy link
Contributor

The first task is used to generate a single mapping, which is used to both create inputs as well as process outputs, right?

@YifanLi86
Copy link
Contributor Author

The first task is used to generate a single mapping, which is used to both create inputs as well as process outputs, right?

Task 1 (urgent, this week): results-processing/visualization based on a particular mapping that user provided (slicing_recovery.csv), no need to develop process to generate the mapping during this task;
Task 2 (next step after Task 1): work on algorithm, generating the mapping and use the mapping to create additional inputs for SWITCH.

@danielolsen
Copy link
Contributor

danielolsen commented May 18, 2021

I think we are on the same page. For the purpose of preparing inputs, there are two tasks: create a mapping, and apply the mapping. For the purpose of processing outputs, we also want to use the same mapping that was used to prepare the inputs. Processing outputs is more urgent, so we will work on code that applies a mapping to outputs (starting with the hard-coded mapping that you've provided), and later we will go back and make code that creates a mapping, and code that applies a mapping for making input files. Yeah?

@YifanLi86
Copy link
Contributor Author

I think we are on the same page. For the purpose of preparing inputs, there are two tasks: create a mapping, and apply the mapping. For the purpose of processing outputs, we also want to use the same mapping that was used to prepare the inputs. Processing outputs is more urgent, so we will work on code that applies a mapping to outputs (starting with the hard-coded mapping that you've provided), and later we will go back and make code that creates a mapping, and code that applies a mapping for making input files. Yeah?

Exactly, we are on the same page.

@danielolsen
Copy link
Contributor

Applying the mapping to generate the timepoints.csv and timeseries.csv files was accomplished via #63, and specifications for generating the mapping should go into #60.

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

3 participants