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

NESP2pt9_BLAZE merge in CABLE-POP_TRENDY #232

Open
1 of 10 tasks
ccarouge opened this issue Apr 10, 2024 · 3 comments
Open
1 of 10 tasks

NESP2pt9_BLAZE merge in CABLE-POP_TRENDY #232

ccarouge opened this issue Apr 10, 2024 · 3 comments
Labels
priority:high High priority issues that should be included in the next release.
Milestone

Comments

@ccarouge
Copy link
Member

ccarouge commented Apr 10, 2024

To consolidate various bodies of work on CABLE, this looks at merging the BLAZE_9184 branch and the CABLE-POP_TRENDY branch. This issue describes the steps taken to achieve this merging and discusses problems that may change the plans.

Goal

The goal is to merge capabilities between the 2 branches. We will try to reproduce the results of the BLAZE_9184 branch although some changes in design might introduce unavoidable differences.
The resulting CABLE-POP_TRENDY needs to keep its current capabilities intact.

Setup

This work will take place in branches stemming from the CABLE-POP_TRENDY branch. It will be integrated into the CABLE-POP_TRENDY branch in instalments.

This pull request shows the differences between the 2 branches. It will update itself as the work progresses.

Testing

We first need to create test cases to compare with:

  • 1000pts serial BIOS3 case:

    • using CABLE-POP_TRENDY branch
    • using BLAZE_9184 branch
  • ACT9 serial BIOS

  • 1000pts + LUC serial BIOS

  • BLAZE-activated test cases?

  • single site tests with/without POP active

  • @juergenknauer to give a list of test cases to ensure we keep the TRENDY functionalities intact.

Work plan

@mcuntz
Copy link
Contributor

mcuntz commented Apr 10, 2024

Dear Claire @ccarouge ,

The CABLE-POP_TRENDY branch comes originally from the NESP2pt9_BLAZE branch. There is already the non-finalised BLAZE code in CABLE-POP_TRENDY. Ben Smith convinced Lars Nieradzik to finalise the implementation of BLAZE but this takes a lot of time because Lars is on it only at 1% of his time. Jürgen and I have promised to merge the two codes once Lars has finished the implementation.

Kind regards,
Matthias

@ccarouge ccarouge changed the title NESP2pt9_BLAZE merge in CABLE-POP_TRENDY BLAZE_9184 merge in CABLE-POP_TRENDY Apr 17, 2024
@ccarouge
Copy link
Member Author

@mcuntz After meeting with Ian Harman and Jürgen, it appears this work would use the branch where Lars is doing his BLAZE work. We haven't decided yet whether merging in BLAZE in CABLE-POP_TRENDY would be part of this work or to keep it in the BLAZE_9184 branch until Lars's work is done. It depends on how complex the merge would be and we haven't had a look at it yet.

@ccarouge ccarouge added this to the BIOS3 milestone Apr 22, 2024
@ccarouge ccarouge added the priority:high High priority issues that should be included in the next release. label May 2, 2024
@ccarouge ccarouge changed the title BLAZE_9184 merge in CABLE-POP_TRENDY NESP2pt9_BLAZE merge in CABLE-POP_TRENDY May 3, 2024
@har917 har917 mentioned this issue Oct 27, 2024
4 tasks
@har917
Copy link
Collaborator

har917 commented Oct 27, 2024

Copying comment from #398 here for connectivity:

In preparing for the work to update BLAZE->CABLE-POP_TRENDY I've had to work a little on this. We need to update the LUH2 data for BIOS - in particular the file/variable names have changed for primary_veg and secondary_veg and there maybe new files needed. (I've had to use the 1 degree versions on rp23 just to get the code to run)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:high High priority issues that should be included in the next release.
Projects
None yet
Development

No branches or pull requests

3 participants