EC-Earth cmor-fixer issues

EC-Earth / cmor-fixer

On-site fixer script for cmorized data

Apache License 2.0

0 stars 1 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Pchengi devel

#40 pchengi opened 3 years ago
0
`list-of-modified-files.txt` empty

#39 uwefladrich closed 3 years ago
2
Run cmor-fixer from arbitrary directory

#38 uwefladrich opened 3 years ago
1
Use path relative to cmor-fixer.py for nemo-vertices and allow for user-defined output directory (into which the list of modified files file is created)

#37 pchengi opened 3 years ago
0
Use the nemo vertices files which are made available on b2share for ece2cmor3

#36 treerink opened 3 years ago
0
Release v3.0

#35 treerink closed 3 years ago
2
Fix lon vertices

#34 treerink closed 3 years ago
0
cmor-fixer failure case: when trying to fix an open netcdf (e.g. with ncview)

#33 treerink opened 3 years ago
0
Add version tracking on data files to fixer

#32 zklaus closed 3 years ago
5
Fix evspsbl

#31 treerink closed 3 years ago
0
Add fix for siconca #28

#30 treerink closed 3 years ago
0
Add fix for evspsbl

#29 treerink closed 3 years ago
2
Add fix for siconca

#28 treerink closed 3 years ago
2
Add fix for ORCA vertices_longitude

#27 goord closed 3 years ago
3
For npp values greater than 1, list of modified files remains empty

#26 pchengi opened 4 years ago
0
Error when executing with --meta flag (release 2.1)

#25 pchengi closed 4 years ago
2
Release v2.1

#24 treerink closed 4 years ago
2
Skipping symbolic links, both dirs and files

#23 goord closed 4 years ago
0
ensure that cmor-fixer ignores symbolic links

#22 pchengi closed 4 years ago
0
Need to make cmor-fixer ignore symbolic links

#21 pchengi closed 4 years ago
1
Complete description.

#20 treerink closed 4 years ago
2
Add nctime to this package

#19 treerink closed 4 years ago
4
Safe olist

#18 treerink closed 4 years ago
0
The version.sh script needs to be less date restrictive

#17 treerink closed 4 years ago
1
Add a savemode solution: if all data is correct do not apply any new tracking_id even with the --forceid option

#16 treerink closed 4 years ago
2
Write immediate successful cmor-fixer action to olist

#15 treerink closed 4 years ago
4
Option --meta to adjust metadata fails

#14 treerink closed 4 years ago
21
Added fix for metadata manipulation

#13 goord closed 4 years ago
0
Parallel proc

#12 treerink closed 4 years ago
0
Add parallel task option

#11 treerink closed 4 years ago
5
Rename fix_lons.py -> cmor-fixer.py

#10 treerink closed 4 years ago
1
Add message to history when cmor-fixer applies modifications

#9 treerink closed 4 years ago
1
Modified list

#8 goord closed 4 years ago
0
Add option with which correct & incorrect data get a new tracking_id

#7 treerink closed 4 years ago
1
Also an LPJG-GUESS fix is needed

#6 treerink closed 4 years ago
1
Release v2.0

#5 treerink closed 4 years ago
4
Add the script which adjusts the version directory name

#4 treerink closed 4 years ago
1
apply fixer only on files generated by ifs, not those generated by LPJG

#3 etiennesky closed 4 years ago
2
Apply or not apply a new track_id when lon data are correct?

#2 treerink closed 4 years ago
4
Add conda environment

#1 treerink closed 4 years ago
1