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

Sda dongchen #3052

Merged
merged 26 commits into from
Oct 21, 2022
Merged

Sda dongchen #3052

merged 26 commits into from
Oct 21, 2022

Conversation

DongchenZ
Copy link
Contributor

Adding template job files specifically for SCC server in BU, and solved several issues so we can not export full year nc files on geo.

Description

Motivation and Context

Review Time Estimate

  • Immediately
  • Within one week
  • When possible

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My change requires a change to the documentation.
  • My name is in the list of CITATION.cff
  • I have updated the CHANGELOG.md.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.


# host specific setup
@HOST_SETUP@
@CDO_SETUP@
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you provide an example of what @CDO_SETUP@ should look like? is that the module command? the path? both?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also dont see a space in Create_Multi_settings.R where you put in the CDO options so that they get written to the XML. Does that info not go into the XML file?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, it should look like "module load cdo/2.0.6", it's SCC specific setup btw.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good point, I am adding it right now.

Copy link
Contributor Author

@DongchenZ DongchenZ Oct 7, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@serbinsh already updated the create_multi_settings script and it's now having the cdosetup in the host section.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dongchen, I see two things that need to happen before I can approve this PR:

  1. The new tags you've added need to be added to the overall PEcAn documentation, including examples like the one in the thread above so that folks know how to use these new tag
  2. These tags need to be added to the SIPNET job template, not the generic model template, for them to work. Furthermore, they need to be there in the default job template, not a geo specific one, otherwise your code will fail. Indeed, the problem you've identified and fixed is in no way specific to BU's geo cluster, only your example module load calls are.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

solved the second point, but I am still working on how to add details into PEcAn documentation.

cdosetup <- ""
if (!is.null(settings$host$cdosetup)) {
cdosetup <- paste(cdosetup, sep = "\n", paste(settings$host$cdosetup, collapse = "\n"))
jobsh <- gsub("@CDO_SETUP@", cdosetup, jobsh)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This statement needs to be outside of the if, otherwise this code will leave the @CDOSETUP@ tag in the job.sh, which will cause the script to fail

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

solved


# host specific setup
@HOST_SETUP@
@CDO_SETUP@
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dongchen, I see two things that need to happen before I can approve this PR:

  1. The new tags you've added need to be added to the overall PEcAn documentation, including examples like the one in the thread above so that folks know how to use these new tag
  2. These tags need to be added to the SIPNET job template, not the generic model template, for them to work. Furthermore, they need to be there in the default job template, not a geo specific one, otherwise your code will fail. Indeed, the problem you've identified and fixed is in no way specific to BU's geo cluster, only your example module load calls are.

@mdietze mdietze merged commit 731f77a into PecanProject:develop Oct 21, 2022
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.

3 participants