Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Yannick then asked if it would be worthwhile to update the findEigen cmake module.  Mark O said there is no need - the way it is done now in oops is to use the NO_MODULE option in find_package - since Eigen has it's own cmake config modules one just needs to set environment variables properly to located locate it, which is done in jedi-stack (e.g. EIGEN_ROOT or EIGEN_PATH to point to the install directory and/or Eigen_DIR to point to the cmake config module).  Mark O added that this is a simpler case than something like LAPACK, which can vary in how it is installed, for example, using MKL in place of lapack or installing with or without cmake modules.  Yannick then asked if findEigen should be removed but it was agreed that it provides backward compatibility that could be useful.

...

Yannick then opened the floor to other build-related issues.  Mark M announced that ODC and Odyssey have been added to the containers, though it's not fully tested.  Odyssey in particular was giving some problems with the intel containers with regard to the python configuration.   This led to a more general discussion on how we should handle python dependencies in JEDI.  For example, as discussed in our Nov 7, 2019 focused discussion, when installing python packages like Odyssey on HPC systems is a challenge because we do not have root privileges.  So, we can only install in user space but then a single installation will not be able to serve all JEDI users as is the case with the environment modules.  As discussed at that previous meeting, it was agreed that the best solution would be to encapsulate all the JEDI python functionality in a virtual environment that each user can install by running pip or an alternative setup script.  Again, this will require some effort so it will not happen immediately.

...