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

Comparison of BLAZE_9184 and CABLE-POP_TRENDY branches #237

Closed
wants to merge 46 commits into from

Conversation

ccarouge
Copy link
Collaborator

@ccarouge ccarouge commented Apr 18, 2024

This pull request is to document the differences between the 2 branches while we start on #232 . This can provide a space for discussion on specific differences or simply an overview of the differences.

core/biogeochem/POP.F90

  • A lot of formatting differences hiding important differences
  • rkill added to Landscape type in POP_types module and ZeroPOP()
  • Changes in ADJUST_POP_FOR_FIRE()
  • Change is INTERPOLATE_FIREMORTALITY()

Updating the formatting in BLAZE_9184 branch would help identifying the scientific differences.

core/biogeochem/casa_inout.F90

Additional variables added for BLAZE

core/blaze

Presumably, we would want to keep these files unchanged from BLAZE_9184. Some differences here are linked to differences in other files (e.g. cable_common.F90)

namelists/cable.nml

We will work from defined configurations outside this repository so differences in this namelist file should not matter.

build differences

We should try and compile the code on various architectures as people will need to run that code on different machines.

lpn599 and others added 28 commits October 27, 2021 15:17
… HYDE-dataset. Instead zero human population density will be used.

- SF%RES has been reset to 0.5 deg as this is the resolution SIMFIRE has been trained on. NEEDS TESTING!


git-svn-id: https://trac.nci.org.au/svn/cable/branches/Share/NESP2pt9_BLAZE@8749 b483b3d9-cc7d-4f55-9e4c-b4562452379e
- Coupling BLAZE-POP fixed 
- Carbon balance fixed (missing removal of carbon from live-biomass) 
- Missing fluxes from fire into the atmosphere have been added to casa-output
Left to do: 
- imbalances due to precision issues 
- tuning of BLAZE for Australia. 


git-svn-id: https://trac.nci.org.au/svn/cable/branches/Share/NESP2pt9_BLAZE@9011 b483b3d9-cc7d-4f55-9e4c-b4562452379e
git-svn-id: https://trac.nci.org.au/svn/cable/branches/Share/NESP2pt9_BLAZE@9084 b483b3d9-cc7d-4f55-9e4c-b4562452379e
git-svn-id: https://trac.nci.org.au/svn/cable/branches/Share/NESP2pt9_BLAZE@9087 b483b3d9-cc7d-4f55-9e4c-b4562452379e
Bugfix for uninitialised variables in cable_canopy.F90. 


git-svn-id: https://trac.nci.org.au/svn/cable/branches/Share/NESP2pt9_BLAZE@9612 b483b3d9-cc7d-4f55-9e4c-b4562452379e
@ccarouge ccarouge added this to the BIOS3 milestone Jul 3, 2024
AlisonBennett and others added 7 commits July 4, 2024 15:19
# CABLE

Thank you for submitting a pull request to the CABLE Project.

## Description

Merge of minor differences in the Spin_1951_draft_ACB branch with the
BLAZE_9184 branch in preparation for merge of BLAZE_9184 into
NESP2pt9_BLAZE.

## Type of change

Branch Merge.

Please add a reviewer when ready for review.
@har917
Copy link
Collaborator

har917 commented Aug 5, 2024

@ccarouge Now that we've merged BLAZE_9184 into NESP2pt9_BLAZE I think this PR - while still relevant - is comparing the wrong pair of branches.

This is preventing the deletion of the BLAZE_9184 branch.

How should we manage this?

@ccarouge
Copy link
Collaborator Author

ccarouge commented Aug 7, 2024

@har917 We are not merging it. But I've updated the branch it will pull from and the title to correspond to our current work plan.

@ccarouge
Copy link
Collaborator Author

ccarouge commented Aug 7, 2024

Forgot I could only change the base branch and not the upstream branch. So closing this and starting a PR for the correct merge.

@ccarouge ccarouge closed this Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants