Closed fzhang0 closed 3 years ago
The weird thing is I don't have this issue. We are both using analysis3-21.07.
Fan is a member of ik11
and can see the file when he does
ls /g/data/ik11/inputs/JRA-55/MRI-JRA55-do/MRI-JRA55-do-1-4-0/atmos/uas/uas_input4MIPs_atmosphericState_OMIP_MRI-JRA55-do-1-4-0_gr_196501010000-196512312100.nc
(I deleted my last post, which was meant for a different issue)
The data in there are symbolic links to the input4MIPs data in /g/data/qv56
:
$ ls -l /g/data/ik11/inputs/JRA-55/MRI-JRA55-do/MRI-JRA55-do-1-4-0/land/friver/*2019*
lrwxrwxrwx 1 aph502 ik11 178 Aug 21 2020 /g/data/ik11/inputs/JRA-55/MRI-JRA55-do/MRI-JRA55-do-1-4-0/land/friver/friver_input4MIPs_atmosphericState_OMIP_MRI-JRA55-do-1-4-0_gr_20190101-20190105.nc -> /g/data/qv56/replicas/input4MIPs/CMIP6/OMIP/MRI/MRI-JRA55-do-1-4-0/land/day/friver/gr/v20190429/friver_input4MIPs_atmosphericState_OMIP_MRI-JRA55-do-1-4-0_gr_20190101-20190105.nc
You need to go to my.nci.org.au and request membership to qv56
I have added a note that qv56
membership is required to access this data in the Notes in metadata.yaml
d'oh I should have noticed that - thanks @aidanheerdegen
The issue has been solved. Thanks @aidanheerdegen
When I try
I get
I don't have this problem when I access other data in ik11.