geoschem / geos-chem

GEOS-Chem "Science Codebase" repository. Contains GEOS-Chem science routines, run directory generation scripts, and interface code. This repository is used as a submodule within the GCClassic and GCHP wrappers, as well as in other modeling contexts (external ESMs).
http://geos-chem.org
Other
167 stars 160 forks source link

Build required software with Spack for GEOS-Chem Classic , Encountering a tricky problem #2233

Open xiaomufeng opened 6 months ago

xiaomufeng commented 6 months ago

Name and Institution (Required)

Name: Institution: Beijing Normal University

Confirm you have reviewed the following documentation

Description of your issue or question

cmake ../CodeDir -DRUNDIR=..

image

my Spack find

image

and my spack env file

image
xiaomufeng commented 6 months ago

In this page, the error is in the screenshot below: https://geos-chem.readthedocs.io/en/stable/geos-chem-shared-docs/supplemental-guides/spack-guide.html#spackguide

image

404 Not Found

yantosca commented 6 months ago

Thanks @xiaomufeng for reporting this. The proper link to the GCClassic sample environment file in the documentation is:

We'll make sure to fix that.

I think I see the problem. The netCDF modules are built for the Intel Cascade Lake architecture, but you are probably using a node that is a different architecture. I would recommend adding target=x86_64 to all Spack library build commands so that they will be built without chip-specific optimizations. This is important if you are using GEOS-Chem on a cluster that has nodes of multiple chipsets. I would rebuild all of the libraries with target=x86_64 and then delete the libraries for the other chip types.

xiaomufeng commented 5 months ago

I'm sorry, according to the method you suggested, I still haven't completed the installation on my end。 Here are some of my operational procedures:

  1. arch

    image
  2. spack find

    image
  3. spack install example

    image
  4. cmake errors

    image
  5. mak -j errors

    image
yantosca commented 3 months ago

Thanks @xiaomufeng for reporting this. The proper link to the GCClassic sample environment file in the documentation is:

We'll make sure to fix that.

@xiaomufeng: Since we have released 14.4.0, the link to the GCClassic sample environment file is now present in the "stable" documentation as well: