Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C CIF
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VERIFY
  • CIF
  • Issues
  • #3

Closed
Open
Created Jul 13, 2020 by Jacob van Peet@vanpeetDeveloper

Path definitions in PyCIF

Summary

Make path definitions in PyCIF relative to the working directory.

What is the purpose of the new feature?

Set the directory for PyCIF output in one location only, and make all other paths relative to that location. For example, when trying to make a monitor file following the steps in the online doc (section 6.2.3 Generate a monitor file compatible with the CIF), the file_monitor parameter was defined as

/some_directory/monitor_reference.nc

which makes them absolute paths in Unix-terms. Probably not meant as such, so would it be possible to use something like

{WORKDIR}/some_directory/monitor_reference.nc

where you set WORKDIR somewhere else?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking