Skip to content
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

Append mode for instantaneous variables #477

Closed
wachsylon opened this issue May 6, 2019 · 4 comments
Closed

Append mode for instantaneous variables #477

wachsylon opened this issue May 6, 2019 · 4 comments
Projects
Milestone

Comments

@wachsylon
Copy link
Collaborator

Hi,
when I try to append data to a chunk of a variable with cell_methods = "time: point", I receive:

C Traceback:
In function: cmor_validateFilename
! 

!!!!!!!!!!!!!!!!!!!!!!!!!
!
! Warning: NetCDF Error (-49: NetCDF: Variable not found) looking for time bounds
! of variable 'mrsol' in file: /work/bm0021/k204210/MPIESMTEST/cmip/archive//CMIP6/ScenarioMIP/MPI-M/MPI-ESM1-2-HR/ssp245/r1i1p1f1/6hrPlevPt/mrsol/gn/v20190506/mrsol_6hrPlevPt_MPI-ESM1-2-HR_ssp245_r1i1p1f1_gnDLFthZ26639.nc
!
!!!!!!!!!!!!!!!!!!!!!!!!!


C Traceback:
! In function: cmor_write
! 

!!!!!!!!!!!!!!!!!!!!!!!!!
!
! Error: time_vals and time_bounds must be passed through cmor_write when in append mode
!
!!!!!!!!!!!!!!!!!!!!!!!!!


Could we enable CMOR to append data of instantaneous variables?
Best regards,
Fabi

@wachsylon wachsylon changed the title Append mode for variables requested with time: point Append mode for instantaneous variables May 6, 2019
@wachsylon wachsylon mentioned this issue May 7, 2019
@taylor13
Copy link
Collaborator

@mauzey1 I think fixing this bug should be a high priority.

@mauzey1 mauzey1 added this to the 3.5.0 milestone Jul 19, 2019
@mauzey1 mauzey1 added this to In Progress in 3.5 Jul 19, 2019
@taylor13
Copy link
Collaborator

@wachsylon @mauzey1 As a note, I think this may be a false identification of the problem. I can't believe no one has tried to append data for instantaneous variables with CMOR3. There's lots of data of this kind in the archive. Can the error be explained by anything else?

@mauzey1
Copy link
Collaborator

mauzey1 commented Jul 26, 2019

@taylor13 With the merging of #480, should we close this issue?

@taylor13
Copy link
Collaborator

Yes, thanks. I'll close it. If @wachsylon thinks the problem hasn't been solved by #480 , then he can reopen.

@mauzey1 mauzey1 moved this from In Progress to Done in 3.5 Jul 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
3.5
  
Done
Development

No branches or pull requests

3 participants