-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xcube gen generates duplicates in time and unsorted time dimension for S2+ #45
Labels
bug
Something isn't working
enhancement
New feature or request
important
This is very important for the project
urgent
High external pressure to address this ASAP
xcube gen
This is related to data cube generation, CLI "xcube gen"
Comments
Maybe a duplicate of #33 ? |
forman
added
bug
Something isn't working
enhancement
New feature or request
important
This is very important for the project
urgent
High external pressure to address this ASAP
labels
May 6, 2019
1 similar comment
forman
added
the
xcube gen
This is related to data cube generation, CLI "xcube gen"
label
May 7, 2019
Closed
AliceBalfanz
added a commit
that referenced
this issue
Jun 21, 2019
AliceBalfanz
added a commit
that referenced
this issue
Jul 11, 2019
AliceBalfanz
added a commit
that referenced
this issue
Jul 11, 2019
Closed
Merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
enhancement
New feature or request
important
This is very important for the project
urgent
High external pressure to address this ASAP
xcube gen
This is related to data cube generation, CLI "xcube gen"
Describe the bug
xcube gen generates two identical time slices with S2+ plugin. In the input data there is only one input file. In addition, the time dimension is not sorted.
To Reproduce
The cube has been produced in xcube-gen with the the following command.
nohup xcube gen --append -v CHL_GILERSON2010_GLOBAL,KdPAR,SPM_VITOnir_SCHELDT,TUR_NECHAD2009_GLOBAL_665 -c /home/xcube/projects/xcube-services/dcs4cop/xcube-gen-configs/dcs4cop-gen_BC_config_S2.yml /data/EOdata/related/DCS4COP/cube_input/VITO/2017//.nc > nohup.out &
The resulting zarr file is still on xcube-gen at /home/xcube/xcube-output/ dcs4cop-bc-s2-sns-l2c-v1.zarr
Note that this issue might be related to the fact that the generation has been interrupted and started again with the same output name.
Screenshots
The text was updated successfully, but these errors were encountered: