Differences between revisions 2 and 3
Revision 2 as of 2023-09-28 17:34:42
Size: 1640
Comment:
Revision 3 as of 2023-09-28 18:32:54
Size: 1603
Comment:
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
  * On Kamioka/Mitaka workstations, environment is already constructed. So you can start to use aligoNB with a following command.
  {{{
$ conda a
ctivate aligoNB
  }}}
  * If you want to c
onstruct a new personal environment, following commands are required.
  * On Kamioka/Mitaka workstations, environment is already constructed. So you can skip this section.
Line 24: Line 20:
  * On the CDS workstation, aligoNB is already installed on {{{/users/Commissioning/aligoNB}}}.
Line 25: Line 22:
$ cd /path/to/somewhere

aligoNB for KAGRA


Environment construction

  • On Kamioka/Mitaka workstations, environment is already constructed. So you can skip this section.
    $ conda create -n aligoNB python=3.9
    $ conda activate aligoNB
    $ conda install -c conda-forge numpy scipy matplotlib nds2-client python-nds2-client gwinc gpstime astropy inspiral-range
    • Though the inspiral-range package is installed via pip in the original installation manual, it's now available on conda-forge.


Installation of aligoNB (not yet)

  • On the CDS workstation, aligoNB is already installed on /users/Commissioning/aligoNB.

    $ cd /path/to/somewhere
    $ git clone https://git.ligo.org/yamamoto/aligoNB.git
    $ git checkout -b kamioka origin/kamioka


How to manage measurement files?

  • On Local NFS disk
    • Only on-site (including Mitaka control room) people can contribute the noise budget activity.
  • On Git
    • We cannot do 'git clone' soon because of too large repositories.
  • On Git-LFS (same way as LIGO)
    • 50GB = $60/year?
    • For a long term usage, more large storage (= much money) is required.

KAGRA/Subgroups/DET/aligoNB (last edited 2023-09-30 20:56:36 by TakahiroYamamoto)