input

  1. Yuan Sun

    Testing IPTpy: Python-Based Input Processing Tools

    Hi all, We are excited to introduce IPTpy, a Python-based input processing tool that generates global 0.9° × 1.25° anthropogenic emissions using CAMS5.3, CAMS6.2, and CEDSv2021_04_21 inventories. We are looking for testers to try out the IPTpy by GitHub clone and provide valuable feedback...
  2. H

    Same Python model and input, but different output on Derecho and local computer

    I am running a moisture tracing model written in Python, on Derecho and my local computer, respectively. When using exactly the same codes and input data, I got slightly different results (which I'd expect to be the same, bit to bit). The differences are small, O(10−16), and only for a small...
  3. marcinkupilas

    Issue with setting start date outside of apparent allowed date range for land initial condition

    I am running free running WACCM compset FWmaHIST on an ne30 grid using a cam development tag cam6_4_028 on Derecho. I set-up the simulation according to f.e23.FWmaHIST.ne30pg3_mg17_L135_c64_005_beres0.70 · Issue #55 · NCAR/wawg_dev, but ran from 2009-12-01. The model ran for a bit over a month...
  4. S

    Setting up bathymetry for experiment

    Hi, everyone, I have some questions about setting up my own experiments, and I was hoping you could help me or direct me to help. I've run some of the examples, gone through some of the notebooks, and watched a tutorial or two. I have a pretty good idea of the roles of different inputs and how...
  5. liyue1

    MPI error (MPI_File_write_at_all) : I/O error (CESM2.1.1 on Cheyenne)

    Hello there! Recently, I'm running the CESM2.1.1 on Cheyenne with a compset of the piControl. The simulation has successfully run for 55 years, and gets stuck in MPI error during last weekend. Below shows the MPI error in the log file: 1: Opened file...
Back
Top