-
Notifications
You must be signed in to change notification settings - Fork 0
Feb2020Minutes
- Jhan & Danny to update us on JaC progress
- UKMO Ticket 940 submitted for JULES-5.7. This "completes" changes needed for CABLE "front end"
- HAC working with 5.6 on Gadi. Verified against 5.5 on raijin. CABLE-CABLE equivalent to CABLE-JULES @ Loobos.
- CABLE mostly waiting on separation of Land/Sea surface fluxes *. JULES-5.8 release "may" include CABLE anyway *. JULES closed release to follow that
- Meeting with JULES/UKMO/UMST Feb 4th
- Increased CABLE presence in 2020 - Proposal raise to have CABLE meeting mid-second half of 2020. Also encourage CABLE presence at CLEX meetings - Martin to consult with Anna
#222 - Climate from zero
#223 - nparams in mpicommon do not match ?revisit - Martin
#237 - labile spinup flag (MDK)
#238 - spincasainput doesn't do anything...
#199 - Tiled vegetation cannot be passed through met file [Fix (Anna says hack - works for site runs) provided, not implemented] -
- recent experience with JAC - #226 'Needs to be tested'
Moved on to March Agenda
Closed Tickets. Comments given within those tickets.
#225 - improved remove_trans logic Revisit when time
#33 - I have embedded this functionality for offline runs in https://github.com/mdekauwe/CABLE_scripts and no one has proposed a solution in 6 years...
#22 - presumably we don't need a ticket for this, it is either being done or forgotten about
#34 - a structure revision is happening as part of JAC, we don't need this.
#37 - 6 years old, if no one is going to do this...then we don't need a ticket.
#55 - what is the status of this float/double thing?
#58 - isn't this also happening as part of JAC, I think we can close this.
#64 - close, there is no description of what it is
#74 - who is this actually a problem for, who is ever going to fix this...?
#75 - this can be closed ... we need to simply obey the MO moving forward
#76- this is a big cable issue...but again unless we fix this, I'm not sure what this ticket offers.
#78 - presumably no one is going to do this, so close
#81 - is this relevant still and if so, how?
#83 - is this different from #55?
#88 - what is the status of the LUC work? This ticket doesn't really say anything?
#89 - was this fixed? It is unclear to me
#96 - what is the status of this?
#104 - what is the status of this?
#105 - was this fixed then, the ticket implies it was?
#114 - close, this simply is an aspiration to do something