Difference between revisions of "Document provenance of results by Allen Pope"
(Added PropertyValue: Expertise = open science) |
(Set PropertyValue: Progress = 100) |
||
| (13 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Task]] | [[Category:Task]] | ||
<br/><b>Details on how to do this task:</b> [[Document the provenance of the results]]<br/><br/> | <br/><b>Details on how to do this task:</b> [[Document the provenance of the results]]<br/><br/> | ||
| + | |||
| + | I looked through the workflow tools. They look good in theory, but with code already done, it was too much of a hassle. Also, not used by my community so not as helpful. MIght also be important that MATLAB is proprietary and didn't look like it was supported? Not sure about gdal. | ||
| + | So, I have chosen to created a fairly detailed workflow diagram, instead (I chose to do this in Illustrator). | ||
| + | [https://www.dropbox.com/s/io0fl64y9f2ns5o/GPF_Workflow.ai?dl=0] | ||
| + | |||
| + | This was a good exercise to align datasets and code. It made sure that I knew all the bits of code I needed (was good to do before sharing code - now that is ready to do, too) as well as all the data. | ||
| + | Gave me an appreciation for the complexity behind what is otherwise a fairly simple description. | ||
| + | |||
| + | I think it will potentially make easier for others to use. | ||
| + | It also made me realize my code is probably not terribly efficient. Something to work on better in the future, not necessarily now. | ||
| + | I also realized that putting together this structure helped me change the way I think about blocks of code, etc - which will be helpful for sharing code later. | ||
| + | It made me think of better ways to structure my code (where to put parameters / how to comment) and how to make it more automated, less hard-coded to particular filenames/landsat scenes. | ||
| + | |||
| + | Consider who did what - and it's a matter of scale (number of authors, processes, etc.) | ||
| + | |||
| + | As a not-formally-trained coder, this made me realize more best practice in terms of creating code. (see above) | ||
| + | |||
| + | One thing which isn't 100% reproducible is the figures. For the map - the GIS is not something I can code up. | ||
| + | For the other plots, I provide a way to get to the point of the figure where possible - but I then have taken it through plot.ly and Illustrator to get to what is in the paper. | ||
| + | I would change how I did this - save the exact code that got me to a figure as much as possible. As well as share the plot.ly itself as an easier way to share things. | ||
| + | |||
| + | Will need to describe in text, too. Break down each sub-section of the workflow, and potentially sketch it out even more broadly at the time of writing. | ||
| + | Potentially make more modular figures, too | ||
| + | |||
| + | Also - need to add code DOIs as appropriate. | ||
| + | |||
<!-- Add any wiki Text above this Line --> | <!-- Add any wiki Text above this Line --> | ||
<!-- Do NOT Edit below this Line --> | <!-- Do NOT Edit below this Line --> | ||
{{#set: | {{#set: | ||
Expertise=Open_science| | Expertise=Open_science| | ||
| + | Expertise=Geosciences| | ||
Owner=Allen_Pope| | Owner=Allen_Pope| | ||
| − | Progress= | + | Progress=100| |
StartDate=2015-03-07| | StartDate=2015-03-07| | ||
TargetDate=2015-03-20| | TargetDate=2015-03-20| | ||
Type=Low}} | Type=Low}} | ||
Latest revision as of 19:06, 6 April 2015
Details on how to do this task: Document the provenance of the results
I looked through the workflow tools. They look good in theory, but with code already done, it was too much of a hassle. Also, not used by my community so not as helpful. MIght also be important that MATLAB is proprietary and didn't look like it was supported? Not sure about gdal. So, I have chosen to created a fairly detailed workflow diagram, instead (I chose to do this in Illustrator). [1]
This was a good exercise to align datasets and code. It made sure that I knew all the bits of code I needed (was good to do before sharing code - now that is ready to do, too) as well as all the data. Gave me an appreciation for the complexity behind what is otherwise a fairly simple description.
I think it will potentially make easier for others to use. It also made me realize my code is probably not terribly efficient. Something to work on better in the future, not necessarily now. I also realized that putting together this structure helped me change the way I think about blocks of code, etc - which will be helpful for sharing code later. It made me think of better ways to structure my code (where to put parameters / how to comment) and how to make it more automated, less hard-coded to particular filenames/landsat scenes.
Consider who did what - and it's a matter of scale (number of authors, processes, etc.)
As a not-formally-trained coder, this made me realize more best practice in terms of creating code. (see above)
One thing which isn't 100% reproducible is the figures. For the map - the GIS is not something I can code up. For the other plots, I provide a way to get to the point of the figure where possible - but I then have taken it through plot.ly and Illustrator to get to what is in the paper. I would change how I did this - save the exact code that got me to a figure as much as possible. As well as share the plot.ly itself as an easier way to share things.
Will need to describe in text, too. Break down each sub-section of the workflow, and potentially sketch it out even more broadly at the time of writing. Potentially make more modular figures, too
Also - need to add code DOIs as appropriate.
