🔬
Emulsion Software notes
  • Personal notes
  • FairShip
    • FairShip installation
    • Software stack test build
    • FairShip geometry
    • FairShip simulation
    • Efficiency of tau neutrino detection
    • Geant4 interface
    • Display tricks
    • Pull request hints
  • SHiP at ECN3
    • Neutrino yield
    • Muon flux
    • Geometry re-implementation
    • Environment
  • SND@LHC
    • Introduction to sndsw
    • Sndsw geometry
    • Simulation Instructions
    • MuonDIS simulation
    • Access simulation output
    • FEDRA reconstruction and csv conversion
    • Reference RUN1 plate 6
    • Local reconstruction in cells
    • Lab operations
  • LASSO
    • Scanning and processing
    • Microscope corrections
    • Calibration
    • Add-ons
  • FEDRA
    • FEDRA software
    • Raw data format
    • Basic workflow
    • Data quality plots
    • Frequently used objects
    • Momentum measurement
    • Vertexing basics
    • Alignment tests
    • Volume-track efficiency
  • Other software
    • FLUKA
    • ELOG
    • Git
    • HTCondor
    • ROOT stuff
    • Openstack
    • Useful code structures
    • 😀Linux useful commands
    • Anaconda
    • Latex tricks
    • DCS
    • PDF annotations
    • ROOT2CAD Conversion
  • Disk usage management
  • SHiPcharm Decay Search
    • Passing simulation to FEDRA
    • Reconstruction used values
    • Proton beam
    • Vtx Identification
    • BDT
    • Analysis of proton interactions and vz fit
    • Decay search
    • Post decay search operations
    • Selections for Matching with Pixel from Christopher Betancourt
  • DESY19 configuration
    • Simulation for DESY19 testbeam
    • Conversion to FEDRA and track reconstruction
    • Shower reconstruction
    • Preparing dataset for ML studies
  • Software installation
    • FEDRA
    • PulseUI
    • Software branches and versions
  • List of mistakes
  • FOOT
    • Introduction
    • Tracking in FOOT sections
    • Vertexing improvement
  • Experimental /Temporary
    • SNDSW neutrino studies
Powered by GitBook
On this page
  • Purpose
  • Test-Building a new stack

Was this helpful?

  1. FairShip

Software stack test build

and again and again and again...

PreviousFairShip installationNextFairShip geometry

Last updated 7 months ago

Was this helpful?

Purpose

During my two year-long astronomical hiatus, one of the few activties I am regularly doing for SHiP is testing new stacks, in support to the Software Coordinator (Oliver).

For this, I am connecting to a Virtual Machine provided by service, where the latest LTS Ubuntu version (currently 22.04) supported is mounted.

The machine is only accessible from lxplus, and it uses my ssh key for access.

Test-Building a new stack

Basically, create a path under the "fake" path /cvmfs/ship.cern.ch/. This naming is used to avoid confusion, when the package will be shipped to the CVMFS file system.

Then, clone the cvmfs_release current master into the "release" with naming convention YY.MM (i.e. 24.09):

git clone --recurse-submodules https://github.com/ShipSoft/cvmfs_release 24.09

Please remember to update shipdist to the latest master (or the version Oliver will point me to)

Then, build FairShip and all related packages as usual:

aliBuild build FairShip --config-dir shipdist --defaults release --always-prefer-system

CERN Openstack