Skip to content
This repository was archived by the owner on Feb 8, 2022. It is now read-only.
This repository was archived by the owner on Feb 8, 2022. It is now read-only.

Failed to create projection #117

@QuentinBrissaud

Description

@QuentinBrissaud

Dear SCEC community,

I recently encountered a problem while setting up UCVM on my local computer (Ubuntu 20.04) using the default installation path.
As described in the wiki, I followed the following steps:

However, once "ucvm_setup.py" successfully finished the installation of UCVM, the "make check" command showed an error while creating the UCVM projection:

Failed to create output UCVM projection +proj=aeqd +lat_0=36.0 +lon_0=-120.0 +x_0=0.0 +y_0=0.0
Proj.4 Error: major axis or radius = 0 or not given
Failed to setup proj +proj=aeqd +lat_0=36.0 +lon_0=-120.0 +x_0=0.0 +y_0=0.0.
Failed to initialize UCVM map

I went through the codes of both UCVM and the proj library to see where it originated (from top to bottom):

  1. p->opj = pj_init_plus(pstr); returns NULL (l. 17) in routine ucvm_proj_ucvm_init in "src/ucvm_proj_ucvm.c"
  2. err = pj_ellipsoid (PIN); is set to 2 (l. 594) in pj_init_ctx which eventually returns NULL (l. 600) in "proj-5/src/pj_init.c"
  3. the condition if (0 != ellps_size (P)) is True (l. 94) in pj_ellipsoid in "proj-5/src/pj_ell_set.c"

I did not go further and I still do not know if the problem I observed was only indirectly related to that condition on "ellps_size" but there seems to be an incompatibility of UCVMC, proj and my local configuration.

My configuration is the following:

  • Ubuntu 20.04 - kernel 5.4.0-050400rc1-lowlatency
  • libopenmpi libraries version 4.0.3-0ubuntu1
  • gcc/gfortran binaries version 9.3.0-1ubuntu2

Note that I also tried to install UCVM with downgraded versions for libopenmpi (3.1.3-11build1) and gcc/gfortran (8.4.0-3ubuntu2) but that did not solve the problem.

There is a similar problem mentioned in the wiki: http://scec.usc.edu/scecwiki/index.php?title=UCVM_User_Guide&redirect=no#Proj._4_Error:_major_axis_or_radius_.3D_0_or_not_given
But in my case, the following is true: "--prefix directory is actually visible to the compute nodes". Therefore, I am not sure how it applies to my problem.

Do you have any idea where the problem could originate from?

Thank you a lot for your help.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions