Hi,
Following the start of the ESM1.6-land standup meetings, we have started a ESM1.6 GitHub project board: ACCESS-ESM1.6 · GitHub
We think it is best to use the same board for everyone so we have a better visibility of the overall project. You can see some instructions about the board in the README
Please consider adding issues to the board and updating status as appropriate.
@dhb599 @sofarrell @anyone?
As usual, feel free to pop any pre-stand up meeting questions here
update: sorry for the delay, just popped the notes from this week’s standup here, please correct/amend.
FYI: @ezhilsabareesh8 has kindly offered to host next Tuesday’s stand up.
@sofarrell reported issues with trying to push changes back to GitHub requesting login credentials and then failing with messages like
Support for password authentication was removed on August 13, 2021.
This is what happens if you clone using the https protocol and then try and git push back to GitHub.
There are a few different solutions.
We’re having a discussion internally to decide on the best approach to use and document properly and we’ll get back to you early next week.
Just noting this in the CABLE developers guide about ssh vs http:
How-to - CABLE Docs
And this flowchart that I’ve found very useful:
Develop your idea - CABLE Docs
Thanks Rachel and Aidan, I was following Chris instructions but this page is useful us well, I will try and monitor what they come up with as a solution next week, and if I need to swap over like your CABLE page suggests, or start again, after the Antarctic conference.
As discussed in the stand-up, I have created an issue to add @dhb599’s iceberg scheme to release-preindustrial+concentrations
@sofarrell and myself are having a (in person!) chat this afternoon regarding the GitHub push workflow (1 and 2) at 3.30pm. Whilst it is in person, we can make it hybrid if other people are interested. @dhb599 we can share our screen if you’re able to make it?
Anyone with an interest in setting up GitHub ssh keys for friction-free GitHub interaction is welcome to come along too. Maybe @tiloz and @RachelLaw might be interested too?
Meeting link is here. Please let me know if you’ll make it.
@cbull - Thanks for the offer but think I’m OK with this part of the process as I’m managing to work with the CABLE repo for a few months now. @tiloz is visiting the University of Melbourne today so I’m guessing wouldn’t be available.
@RachelLaw, okay, no worries at all. 
To be clear, the workflow discussed here, gives the user an option to use https or ssh keys and the former will not allow you to push. Are you using ssh keys? Or in other words, have you successfully pushed to the remote GitHub repository?
Rachel is all set. She followed the CABLE setup which is using SSH keys. And she is successfully pushing to CABLE (now 
)
Meeting notes from yesterday are up. @dhb599 @sofarrell please correct/amend as appropriate.
I’ve asked @Aidan about the discussed permissions issue.
Update: @Aidan and @cbull looked into the permissions problem from last week. There was a small mistake in which only read permissions were given on cice4 which is likely the problem was for @dhb599. This has now been corrected.
Hence, @sofarrell and @dhb599 can you please try to push again? I think it should work now…
(@sofarrell cice5 did not have that problem so should be working and is unchanged from last week.)
@Aidan, @pearseb, @RachelLaw, @dhb599, @harshula, @anton, @sofarrell, thanks for coming along today.
Minutes are now here, please correct as appropriate.
I have a meeting a 9am tomorrow, I probably won’t make the 9:45 meeting. I am progressing the changes to the spack package to build cice5 for esm1.6, hopefully that gets merged this week (and then be available when Dave & Siobhan have updates to cice5 & its coupling)
There’s also a NESP Climate Systems Hub science day tomorrow so I think that means me, Dave and Pearse won’t make it to the standup.
Ok, thanks for the update @RachelLaw.
I’ll pop into our usual room at 9.45am.
Feel free to pop items here if you’re coming and have something you’d like to discuss.
I think the item I wanted to discuss needs @dhb599 and @pearseb there as well so we should hold it over to the following week.
Regarding tomorrow’s standup, can we please all meet here instead
Facilitates breakout rooms.
See you soon!
Minutes from today’s standup are here. Please correct/amend as needed.
See you all next Tuesday, here
Following CSIRO team meetings yesterday and today, we have put together this table.
The first three columns are cases that we are already running. Case 1 (in italics) is an intermediate case that we now think we can skip over. Case2/3 are the ones we’d like to focus on for the summer.
For the ocean/sea-ice, we think the priority is getting the iceberg code changes in. Can @dhb599 work with @pearseb and @cbull (or team member) to get this going this week? The iceberg scheme uses runtime parameters, so we also need help with how this works under payu.
We think including CICE5 may need to wait until next year.
I’ll send invitations shortly for a ‘hackathon’ next Tuesday for those who can make and are able to contribute.
