search

PecanProject / pecan

The Predictive Ecosystem Analyzer (PEcAn) is an integrated ecological bioinformatics toolbox.
www.pecanproject.org
Other
202 stars 235 forks source link

Append year to file name in met workflow #265

Closed jam2767 closed 9 years ago

jam2767 commented 9 years ago

Mike, Betsy, and I have been discussing when to sort met files into yearly files and where to denote the year in the file name. The preference is to do this early on in the workflow (met2cf) to avoid any problems downstream. The met2model functions all assume the format of prefix then year (e.g. prefix_maybe other info_year.nc) to do the parsing. Is everyone OK with doing this file renaming in met2cf and do you see any problems with converting file names to this format?

ankurdesai commented 9 years ago

Makes sense to me.

Ankur R Desai, Associate Professor University of Wisconsin - Madison, Atmospheric and Oceanic Sciences http://flux.aos.wisc.edu desai@aos.wisc.edu O: +1-608-520-0305 / M: +1-608-218-4208

On Dec 1, 2014, at 10:25 AM, jam2767 wrote:

Mike, Betsy, and I have been discussing when to sort met files into yearly files and where to denote the year in the file name. The preference is to do this early on in the workflow (met2cf) to avoid any problems downstream. The met2model functions all assume the format of prefix then year (e.g. prefix_maybe other info_year.nc) to do the parsing. Is everyone OK with doing this file renaming in met2cf and do you see any problems with converting file names to this format?

— Reply to this email directly or view it on GitHub.

apourmok commented 9 years ago

Sounds good.

On Mon, Dec 1, 2014 at 11:28 AM, Ankur Desai notifications@github.com wrote:

Makes sense to me.

Ankur R Desai, Associate Professor University of Wisconsin - Madison, Atmospheric and Oceanic Sciences http://flux.aos.wisc.edu desai@aos.wisc.edu O: +1-608-520-0305 / M: +1-608-218-4208

On Dec 1, 2014, at 10:25 AM, jam2767 wrote:

Mike, Betsy, and I have been discussing when to sort met files into yearly files and where to denote the year in the file name. The preference is to do this early on in the workflow (met2cf) to avoid any problems downstream. The met2model functions all assume the format of prefix then year (e.g. prefix_maybe other info_year.nc) to do the parsing. Is everyone OK with doing this file renaming in met2cf and do you see any problems with converting file names to this format?

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/PecanProject/pecan/issues/265#issuecomment-65090887.

Afshin Pourmokhtarian, Ph.D. Postdoctoral Research Associate Dietze Ecological Forecasting Lab Boston University Deptartment of Earth & Environment, Rm 130 685 Commonwealth Avenue Boston, MA 02215