Project

General

Profile

Support #23419

Request patch release v08_27_01_01 for ProtoDUNE production

Added by Tingjun Yang 29 days ago. Updated 5 days ago.

Status:
Assigned
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
10/14/2019
Due date:
% Done:

100%

Estimated time:
Spent time:
Experiment:
DUNE
Co-Assignees:
Duration:

Description

Dear larsoft experts,

We would like to request a patch release v08_27_01_01 to address the issue of tensorflow using too many CPUs. This release will be based on v08_27_01 and have feature branch feature/lhw_tfFix merged in larreco.

Thanks,
Tingjun

History

#1 Updated by Lynn Garren 29 days ago

  • Assignee set to Thomas Junk
  • Status changed from New to Assigned
  • Co-Assignees Tingjun Yang added

Branch v08_27_01_br has been created. It is now up to you to make the release. Recall that instrucions are on the LArSoft wiki: How to tag and build a LArSoft patch release

I think both Tom and Tingjun have appropriate permissions. We are happy to provide advice if you encounter any difficulties.

#2 Updated by Lynn Garren 15 days ago

Files in larsoft/releaseDB have been modified so that artdaq_core v3_04_20a will be built as part of this distribution.

#3 Updated by Tingjun Yang 10 days ago

I noticed startPatchRel only checks out develop branch for experiment code except uboone. For example:

  elif [[ ${experiment} == "dune" ]]; then
  echo "checkout dunetpc" 
  mrb g dunetpc
  echo "checkout duneutil" 
  mrb g duneutil

For uboone:

  elif [[ ${experiment} == "uboone" ]]; then
  echo "checkout uboonecode" 
  mrb  g  -b ${expbranch} uboone_suite

#4 Updated by Tingjun Yang 10 days ago

Also artdaq_core v3_04_20a depends on cetbuildtools v7_13_02 while other packages depend on cetbuildtools v7_12_01. Is this a problem?

#5 Updated by Lynn Garren 8 days ago

The version of cetbuildtools is often different for various packages. mrb will setup and use the newest version of cetbuildtools. This is meant to be transparent to the user.

startPatchRel usage:

Usage: startPatchRel <working_dir> <experiment> <new patch tag> <larsoft branch> [<experiment branch>]
   create subdirectory <working_dir>/<new patch tag>, run newDev, then checkout larsoft_suite and experiment code
   create subdirectories for e17 and c2 builds

   experiment must be one of argoneut, dune, lariat, icarus, sbnd, or uboone

If the experiment branch is not specified, startPatchRel will use the same branch as the larsoft branch. If a branch does not exist in a repository, then it remains at the head of develop. It is always wise to double check before starting any work.

#6 Updated by Tingjun Yang 6 days ago

Thanks to Lynn's help, I have tagged and installed larsoft v08_27_01_01:
https://cdcvs.fnal.gov/redmine/projects/larsoft/wiki/ReleaseNotes08270101

#7 Updated by Tingjun Yang 6 days ago

  • % Done changed from 0 to 90

Tom provided dune_raw_data v1_17_35_01 and lbne_raw_data v1_04_36_01 and I have tagged dunetpc v08_27_01_01. I confirm it resolves issues #23427 and #23509.

I am building dunetpc v08_27_01_01 on Jenkins.

#8 Updated by Tingjun Yang 5 days ago

  • % Done changed from 90 to 100

dunetpc v08_27_01_01 SL prof builds are installed.



Also available in: Atom PDF