Joint vision: Future GliderTools package structure #107
Replies: 5 comments 7 replies
-
Related tool: I'll be working on gliderpy this summer. I'd love to make it easy to pass glider data downloaded from an ERDDAP server into GliderTools |
Beta Was this translation helpful? Give feedback.
-
From the discussion today it seems to me (might be overlooking something here), that we should clarify (and perhaps modify) they representation of gliderdata that glidertools expects. It seems that the most 'raw'/general way to pass data is in form of a 'timeseries' or 1D array (where time is the only real dimension, and other values like depth/lon/lat ... are coordinates). A common 'higher level' product is a profile 2D array that has some form of depth coordinate and a profile index. Then there are even higher level 'derived' products (mapped 3/4D data), but these are not easily convertible back and forth, so I will exclude them here. From @callumrollo excellent demo notebook I take that glidertools commonly uses the former 1D representation, but certain applications might favor the 2D one (@castelao is this echoing some of your concerns you raised during the call today?). glidertools is nicely positioned to do this conversion, and assure that the roundtrip conversion does not loose any data. Tools that build on that could then choose between either representation of the data. @kerfoot mentioned that his tool was able to convert between these two? Perhaps we could refactor that into the main glidertools package (and move some of the I/O related code from there to either your package or another intermediate one. |
Beta Was this translation helpful? Give feedback.
-
Meeting notes from GliderTools / OceanGliders Best Practice Workshop Session chairs: I. Giddy, T. Ryan-Keogh, D. Balwada, C. Rollo, S. Thomsen, S. Nicholson Discuss on future vision of package structure and overall GliderTools community. Participants Link to google doc |
Beta Was this translation helpful? Give feedback.
-
One of the question that came in was better defining the focus of Glidertools. If people post here what they think the focus of GT is and should be, in broad terms, then I can help rewrite the intro page. For example someone raised the point that they want to allow people who have no coding or oceanography experience to be able to explore the data. I think that is a great use case, but definitely not something that we are trying or want to achieve with GT. In my opinion: |
Beta Was this translation helpful? Give feedback.
-
A second vision for the Glidertools community (not GT package) can be documenting the process for doing different analyses. Callum's demo notebooks show how this can be done for some of the options available in GT (https://github.com/GliderToolsCommunity/glidertools-demo). However, we can even think bigger and create a place for people to share notebooks that use GT as the base (or not), but then have to use other packages to achieve other specific goals (e.g. I can think of @isgiddy spectral analysis as one example). In the long term, this can be very helpful to new users of gliders. |
Beta Was this translation helpful? Give feedback.
-
Hi everyone,
As promised I worked on a draft figure for a new package structure. Some of you have already contributed to this proposal. Thanks a lot for your input. I tried to follow the data lifecycle (left to right). You can click on the figure to expand it.
At this stage the main goal is to develop a joint vision.
(1) So please feel free to comment on it
(2) State where you might want to contribute.
(3) Do you already have a software package which could be implemented or made compatible with GliderTools?
(4) Are you working on something right now which could be aligned with this community effort? Maybe you can get support?
If you want to make direct changes to the figure (within the MIRO board), please let me know. I can give you access.
Best Soeren
@lukegre @jbusecke @dhruvbalwada @callumrollo @isgiddy @tjryankeogh @marcelduplessis @tomhull @bastienqueste @AnthonyBosse @castelao @patricialg @sarahnicholson @sebswart @AlicePietri @dennisstanley64 @sryan288 @LewisDrysdale @backeb @nlbeaird
Beta Was this translation helpful? Give feedback.
All reactions