Comments (9)
hi @ehogan the uvcdat-2.4.0
was simply a tag for UV-CDAT since CMOR is distributed as part of UVCDAT we wanted to make sure that user building uvcdat 2.4.0 would always get this version of cmor. @nadeau4 and I will take a look at your issue and make sure it is solved in the upcoming 3.0 release. Thanks!
from cmor.
That sounds great @doutriaux1, thank you very much! :)
from cmor.
ehogan,
I am working on CMOR 3.0 and I have an alpha release in branch cmor3 due today. You will need to install the json tables found in https://github.com/PCMDI/xml-cmor3-database/tree/master/src and there is a new library called libjson-c that needs to be installed and passed to the configure. I should have more documentation by the end of the day.
Denis
from cmor.
@dnadeau4 let's make sure that her bug is fixed in this release, thanks.
from cmor.
@doutriaux1 @dnadeau4 I think the point raised by @ehogan is a good one.
Why not just tag the CMOR version for the UV-CDAT release with the current CMOR release - so 2.9.3
or 2.9.2
rather than create an arbitrary duplicate tag/release point. The intention is to lock versions, so whether this is a tagpoint named uvdat-2.4.0
or 2.9.2/3
it achieves the same aim
from cmor.
Yes especially since for CMOR master is always the latest stable version. That makes sense.
from cmor.
@doutriaux1 well master
keeps moving, 2.9.3
(or similar) shouldn't..
from cmor.
@durack1 yes but I was saying that we don't need a uvcdat specific tag point since uvcdat uses master and master is always at some tag point.
from cmor.
master has now been moved to CMOR 3.1.0
from cmor.
Related Issues (20)
- Exposing latest netcdf 4.9.x library functionality: quantize, zstandard HOT 13
- Remove unused attributes when processing CMIP6Plus datasets HOT 14
- Exposing latest netcdf 4.9.x library functionality: quantize, zstandard HOT 48
- unclear warning... HOT 5
- bounds required on singleton lon and lat? HOT 5
- avoid attributes of bounds of auxilliary coordinates (`vertices_latitudes` / `vertices_longitude`) HOT 5
- Calibrating CMOR3 & 4 forward development plans HOT 7
- CMOR 3.8.0 Release HOT 4
- Update README.md to remove v3.7 reference
- default `realm = "REALM"` is always written although not required by CV HOT 2
- order in `required_global_attributes` matters HOT 1
- input time type as INT HOT 3
- CircleCI current image deprecated HOT 1
- Numpy 2.0 compatibility issue HOT 2
- File output size and chunking HOT 10
- Message Logging generates duplicated output lines
- DESTDIR support HOT 2
- Failure invoking set_deflate HOT 1
- user defined grid mapping
- Add CITATION.cff file HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cmor.