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

Offshore wind energy files #18

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

Offshore wind energy files #18

wants to merge 5 commits into from

Conversation

zcranmer
Copy link

I added all the files I'm using to include offshore wind energy in GCAM-USA. Offshore wind is included globally and in each state in the US. The Matlab code generates much of the data in the csv files. I can provide any results that you would like to see and I can provide my dissertation chapter as well. There are some bugs, particularly under high carbon taxes, there are some solution errors.

Zana Cranmer added 5 commits June 28, 2017 11:02
batch files include all xml files needed for each offshore wind cost case.
Matlab code and data inputs to create offshore wind energy supply curves
xml files with all the data for each offshore wind technology for each cost case.
files to convert csv files into xml files for offshore wind
data input files for offshore wind energy -- some are edited by the matlab code, some just create the offshore wind technology names.  I used onshore wind as the model for these files.
@rplzzz
Copy link
Contributor

rplzzz commented Jun 28, 2017

@zcranmer Thanks for your contribution. I think that in order to evaluate this pull request we will need a write-up that describes:

  1. The purpose of the work. What is the problem that it is trying to solve, or science question it is trying to answer?
  2. The approach taken in the work. This would include both a description of the theory behind your approach, and a description of how that was implemented in software. How does your proposed solution achieve the objectives laid out in the previous section?
  3. An evaluation of the results. What changes as a result of the new work? How do those changes improve the results relative to the baseline scenarios?

It sounds like you might have some of this in your dissertation chapter, so that might be a good place to start. Depending on what you have written, you might want to edit it down to just the parts that are relevant to the items in the list above.

@zcranmer
Copy link
Author

I've attached part of the chapter from my dissertation describing our question and the methodology (Methodology.pdf). The implementation in GCAM was modeled on onshore wind. For validation, I could provide a comparison of cases without offshore wind to cases with offshore wind. What outputs in particular would be most helpful?

@ssmithClimate
Copy link
Contributor

Thanks @zcranmer for submitting this! @rplzzz, Zana also has a paper submitted (or soon to be?) that will ultimately also serve as a documentation source.

@zcranmer
Copy link
Author

@rplzzz and @ssmithClimate The paper is preparation and hopefully will be submitted soon! So happy to share results, but preferably privately until that's submitted.

@ssmithClimate
Copy link
Contributor

No need to make the paper public. I suspect your dissertation chapter is enough for the moment.

@robbieorvis
Copy link

Is there a way to download these files easily? I can't seem to figure it out... (forgive my ignorance)

@mbins
Copy link
Contributor

mbins commented Mar 15, 2020

@robbieorvis It looks like you may be able to do this on the command line: https://stackoverflow.com/questions/52598824/git-download-pull-request-files-changed. Note that I haven't tried this myself. I haven't seen an easy way to do this from the web interface.

@robbieorvis
Copy link

I was actually able to do this by cloning @zcranmer's gcam-data-master folder, but the included files are incompatible with GCAM 5.0 and later, so I'm giving up for now.

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 this pull request may close these issues.

5 participants