Monday, May 4, 2020

GEOframe Community Publication Policy (GCPP v 1.0)

After GEOframe is becoming widely used we believe it is time to set some fair rules for participation to GEOframe related publications, Since the components are usually released under GPL3 license, it allows the of the code almost without any restriction (except the maintaining the derived code Open Source and freely available), a condition mitigated by the fact that different OMS components can be released under other licenses.  However, because all of our recognition derives from publications (and proper citations), it is worth to remark what written below (partially derived from Jules community publication policies):


GEOframe Community Publication Policy (GCPP v1.0)
  1. Introduction
GEOframe-NewAge is an open-source, semi-distributed, component-based hydrological modeling system. It was developed in Java and based on the environmental modeling framework Object Modeling System V3 (OMS3). 
The core of the project was born from the idea of Professor Rigon and mainly developed at the department of civil, environmental and mechanical engineering of University of Trento, Italy. During the last decade, GEOframe community grew and now is made of many scientists around the world who share their work, codes, knowledge and experiences for the benefit of all GEOframe users, whilst pursuing their individual research interests and careers.
Therefore, giving appropriate credits for the intellectual input through co-authorships or citations should be the proper functioning of the community.
This document sets out how members of the GEOframe community should recognise the intellectual contribution of the GEOframe community’s members. 
  1. Principal web references
In the following, the principal GEOframe web references, where you can find the latest achievements, developments, publications, code versions, courses and ideas are reported: 
  1. General principles
The formal, legal conditions that govern the use of GEOframe at present are given by the G.P.L. v 3. Each GEOframe component can have its own license though. 
This Policy applies to all uses of GEOframe products, including but not limited to data and computer code, for research and teaching. It is not intended to restrict what can be done with them, rather to ensure appropriate acknowledgement and communication between users and developers. This policy will be updated regularly.
A developer is any person whose expertise has either significantly influenced the design of GEOframe code or who has written code, with no distinction between scientific and technical inputs.
Developers are encouraged to publish their work in reasonable time, while potential users should approach developers early in their study to avoid duplication or wasted effort on new developments. Developers may reserve the right for the first scientific application of their scheme and will be able to advise if and when co-authorship, citation or acknowledgement is appropriate. 
A list of new developments and the scientists responsible for them will be maintained on the GEOframe website. These contributions should be recognised by citations.
When writing the source code of a component, GEOframe developers should consider the following:
  • Provide a brief description of what the program does.
  • State the authors of the code and the following modifiers.
  • Describe the input required to run the component and its output.
  • Some notes concerning the limitations, and the algorithms used within the component. A wish-list for the future version and/or information.
  • Articles or books which have inspired the codex or justified its necessity. Users are encouraged to cite these papers in their own work.
  • A more detailed documentation about the code can be found in (link alla pagina con la documentazione delle componenti e il template per LaTeX.
  • If you want to contribute code or documentation, create pull requests, we will consider them.
Ideally a committed code should conform to the rules required by Joss. 
Acknowledgments should be considered for a wider list of scientists who contributed to the modelling system, but whose contributions may not be documented in publications. A list of such scientists will be maintained on the GEOframe web page
When writing a paper, GEOframe users and developers should consider the following:
Co-authorship  
  • Is expected if your research benefited from a new development, i.e. the development influenced your study to the extent that it was discussed in the paper. 
  • Is expected if your research required substantial direct input from a developer, e.g. to make substantial modifications to the code that you used, to help design the experiments etc.
  • Should be considered for a wider list of scientists who contributed to the modelling system, but whose contributions may not be documented in publications. A list of such scientists will be maintained on the GEOframe web page.
  • Developers cannot claim the first (or primary) authorship of a paper where they did not contributed in writing and conceiving the main research topics. 
Acknowledgements 
  • Should be considered for scientists involved in GEOframe code developments that have become established.
Citation of a published paper 
  • Is expected if a citable paper describing a development exists. A narrative description of the model and a list of papers describing developments will be maintained on the GEOframe web page.
Please be generous in offering credit for other people’s work, as everyone benefits in the end. Use best judgement and, if in doubt, err on the side of inclusiveness.

You can find the pdf and Epub version of the document by clicking on the links. For the readers can also be interesting to consider the reading of About Authorship in Hydrology.

Friday, January 24, 2020

GSW2020 - Photos and material

You can see here some photos of the GEOframe Winter School 2020. The material and the final refine OMS/GEOframe GWS2020 project can be found on
It contains all the needed input and output files for executing the School's project. It will not work if you do not do all the right operation. Therefore, please browse the school material in order starting from the first post.

Previous Winter School Page                      All pages                           First Page

Friday, January 17, 2020

GWS2020 - The Bonus II: Richards equation treated better better than in Hydrus 1D

The second bonus of the GEOframe Winter School on GEOframe is about the Richards' equation. Here we present the ongoing work by Niccolò Tubini (AboutHydrology) in his doctorate. In particular he is presenting how his code is working and why we believe it is a good code.
The presentation by Niccolò is divided into 2 parts: I and II.  The illustrated Jupyter Notebook as wells as the codes can be dowloaded from Github. There you can find also the Jupyter Notebooks and also browse the other software, including the Richards1D version coupled with the energy budget.


GWS2020 - The Bonus I: A little on Travel Times

In the last days of the GEOframe WinterSchool 2020, most of the time was dedicated to simulating with the software but we also give a little clue on  topics that we could not expand more. This is the case of travel times modelling (and/or residence time).  Here Marialaura Bancheri (GS, Abouthydrology) talks a little about the theory and the applications she did mainly in her thesis.
You can watch the video of her talk here.  So far we did just the application that can be seen In Marialaura's thesis which are mostly demonstrative that real. Soon, however, in the project WATZON, we will use them massively.


Previous Winter School page

Tuesday, January 14, 2020

GWS2020 - Rainfall Runoff

Here we are introducing some modules for rainfall runoff modelling present in GEOframe.  We also maintain some material of the 2019 GEOframe Winter School that can be though interesting.



Cavone River Exercise
Goodness of fit notebooks



General references to Rainfall-Runoff

Beven, K. (2012), Ranfall Runoff, the primer, Wiley-Blackwell

Rigon, R., Bancheri, M., Formetta, G., & de Lavenne, A. (2015). The geomorphological unit hydrograph from a historical-critical perspective. Earth Surface Processes and Landforms, http://doi.org/10.1002/esp.3855

References besides the one already used

For seeing how to represent lumped hydrological models (you can give a look to this paper here)

Abera, W.W. (2016), Modelling water budget at a basin scale using JGrass-NewAge system. PhD thesis, University of Trento

Bancheri, Marialaura (2017) A flexible approach to the estimation of water budgets and its connection to the travel time theory. PhD thesis, University of Trento.


Bancheri, M., Serafin, F., & Rigon, R. (2019). The Representation of Hydrological Dynamical Systems Using Extended Petri Nets (EPN). Water Resources Research, 8(01), 159–27. http://doi.org/10.1029/2019WR025099


Bancheri, M., Rigon, R., & Manfreda, S. (2020). The GEOframe-NewAge Modelling System Applied in a Data Scarce Environment. Water, 12(1), 86–24. http://doi.org/10.3390/w12010086

Formetta, Giuseppe (2013) Hydrological modelling with components: the OMS3 NewAge-JGrass system. PhD thesis, University of Trento.

Formetta, G., Antonello, A., Franceschi, S., David, O., & Rigon, R. (2014). Hydrological modelling with components: A GIS-based open source framework, 55(C), 190–200. http://doi.org/10.1016/j.envsoft.2014.01.019

Patta, C, Costruzione di un modello idrologico di stima della disponibilità idrica in area pedemontana, Tesi di laurea (in Italian), Politecnico di Torino, 2018

For open questions about rainfall-runoff see also the Meledrio Posts.

GWS2020 - Evaporation and Transpiration

Evapotranspiration accounts for most of fifty percent of the terrestrial hydrological cycle. We illustrate here some ways to estimate it with the tools offered by the GEOframe system. 

Radiation

We do not cover radiation in this school. We will just use it. For people interested, however, they can give a look to the material of 2019 School here.


The 2020 material



The 2019 material
Out of schedule (for Chhay)
Exercises
References

Primarily for historic papers browse to the list by Dennis Baldocchi
See also the discussions here:

Friday, January 10, 2020

The Jupyter notebooks and OMS project repository for the WSG2020

During the classes we use several Jupyter notebooks. You can find them at the appropriate OSF page:

Jupyter Notebooks

So if you search a notebook and you do not know where to find them: they are here.

The OMS project used is instead here:

Overall OMS3 project (available on Zenodo). It contains all the software used in the school.