search

plantphys / gsti

A project focused on the development of generalized spectra-trait models for the prediction of leaf photosynthetic capacity. This includes models focused on the prediction of leaf nitrogen, leaf mass per area (LMA), leaf water content (LWC), Vcmax, Jmax and dark respiration.
GNU General Public License v3.0
6 stars 1 forks source link

Replace "Global_Vcmax" with a new, more appropriate name for the effort/rep #35

Closed serbinsh closed 1 year ago

serbinsh commented 1 year ago

Global Vcmax isnt very descriptive, doesnt really convey what this is, and doesnt contain spec.

serbinsh commented 1 year ago

Re-upping this for discussion to provide a more appropriate name for this effort.

regnans commented 1 year ago

No great ideas, but hopefully my brainstorming can inspire something better. Long form: "Prediction of leaf photosynthetic capacity using a global spectra-trait model" Short form: I'm not sure where to start. The "Glob_something" type names have been used a lot before, and we don't want to be confused with other data assimilation efforts. "Earth_Leaf_Capacity" "Global_assimilation_prediction" "Unified leaf trait predictor"?

alistairrogers commented 1 year ago

Global Spectra-trait Initiative, Global spectra-trait partnership. or something like that. I think its OK to have a broad name for the project. The landing page will state our initial focus on photosynthetic and related traits. I don't think we need to cover the whole spectrum of potential work in this first effort or design a future-proof workflow or structure. Broad name, but limited initial focus. A broad name would allow us to pitch this idea to different sponsors with he initial example of photosynthetic traits. Happy to help draft some landing page text if you want.

serbinsh commented 1 year ago

I think we need to remember to separate the description from the name. We need a short, snappy name to label the git repo and then we can elaborate in the readme/description. So I like something like "Global Spectra-trait Initiative" but where we label the repo TESTgroup-BNL/gsti, or TESTgroup-BNL/GSTI, or something like that. the repo name shouldnt have a very long name if we can avoid

As a reminder with Ben's COSOSRE its the COntinuous SOil REspiration community database https://onlinelibrary.wiley.com/doi/full/10.1111/gcb.15353

with the repo URL: https://github.com/bpbond/cosore

So @regnans or @alistairrogers suggestions are good if make them acronyms for the repo name/URL and then define them straight away in the readme

DavidsonKen commented 1 year ago

I think the acronym "GSTI" works well. Better than "PoLPCuaGSTM" and it leaves the project open to change and improve in the future

regnans commented 1 year ago

GSTI doesn't have too many existing conflicts. It appears to be the name of a possibly defunct software business in New Jersey, and is the stock market code for Pineapple Express Inc. And 240 GitHub repos have "GSTI" in the name, although mostly as only part of the name.

"PoLPCuaGSTM" probably has no conflicts, but it's not pretty! Or readily meaningful.

serbinsh commented 1 year ago

Yeah - I forgot to check for other repos named the same, e.g. as you say

https://github.com/Gcaufy/gsti

I suppose that is OK since the URL will be including our org path and i expect to release with Zenodo DOIs so should not be hard to find

JulienLamour commented 1 year ago

Ok! Great name!