art series 2.02¶
Previous series release notes
Next series release notes
New features¶
Expanded configurability of RootOutput¶
The options for specifying output-file switching have been enhanced. It is now possible to specify a maximum number of events, subruns, runs, and/or input files for a given output file. See the output-file handling documentation for details. Note that there are some breaking changes from art 2.01.02 to 2.02.00 for the RootOutput configuration. To glean what these are, please see the aforementioned link. For most users, it is unlikely that any configuration changes are required. (Resolves feature request #13273.)
Relaxed @protect_ignore specification¶
It is no longer an error to re-use the @protect_ignore: binding modifier on the same FHiCL key. This change in behavior introduces a new version of the FHiCL language: FHiCL 4. See the issue description in feature request #12877.
Support for partially validated configurations¶
For cases where an entire configuration cannot be subjected to validation, a DelegatedParameter class has been added in fhiclcpp. See the DelegatedParameter documentation for details.
Improved diagnostic messages for FHiCL parsing¶
For parse errors encountered in prolog declarations, users will now receive detailed annotations specifying the location of the error (resolves feature request #13363).
Breaking changes¶
- Various aspects of
messagefacility have changed. Although this is unlikely to affect most users, please peruse the messagefacility version 1.17 release notes to determine if any action should be taken for your particular use cases.
art releases¶
art suite 2.02.02art suite 2.02.02
art suite release notes 2.02.02 (2016/08/08)¶
Bug fixes¶
- Issue #12990:
rapidjson has been removed from canvas--it is used only in art and already exists there.
- Issue #13272: Spurious output files are no longer produced in the
artdaq context whenever RootOutput file-switching is configuration (also resolves issue #13174).
- Issue #13464: A segmentation violation encountered when initializing
messagefacility in single-threaded mode has been fixed.
Known issues¶
- A new required link-time dependency on
ROOT_CORE was discovered for services. Although this dependency was introduced in art 2.01.00, it was first noticed here. This issue has been resolved in art 2.03.00.
Dependent packages¶
art suite 2.02.01art suite 2.02.01
art suite release notes 2.02.01 (2016/08/02)¶
The feature set of this version is identical to that of art 2.02.00. The only difference is the incorporation of the patched ROOT version (6.06.04b), which includes the memory-leak fix mentioned in the version 2.02.00 release notes.
External package changes¶
| Package |
art 2.02.00 (previous) |
art 2.02.01 (this version) |
root |
v6_06_04a |
v6_06_04b |
Dependent packages¶
art suite 2.02.00art suite 2.02.00
art suite release notes 2.02.00 (2016/08/02)¶
External package changes¶
The table entries marked by "--" correspond to versions that exist in one art release but not the other.
| Package |
art 2.01.02 (previous) |
art 2.02.00 (this version) |
Notes |
igprof |
-- |
v5_9_16 |
Added to distribution |
Bug fixes¶
- Issue #11648: The dependency of the
cetlib checksum implementations on polarssl has been removed in favor of native implementations.
- Issue #13055: The
MemoryTracker and TimeTracker services are now safe against potential uncaught exceptions thrown from their members' destructors.
- Issue #13321: Fix for inappropriate exception throw in situations where the deprecated
services.scheduler.fileMode parameter was specified and no output modules were configured.
Known issues¶
- ROOT memory leak: This version of
art uses ROOT v6_06_04a, which has known memory leaks in ROOT's fitting routines. If your experiment heavily uses ROOT's fitting algorithms in its production jobs, using this release may be unfeasible. The patched version of ROOT (v6_06_04b), which does not have the leak, is included in art 2.02.01.
- When using
messagefacility in the single-threaded mode, a segmentation violation is encountered at initialization. Although this does not affect users of art per se, which uses the facility in multi-threaded mode, it can cause problems for users initializing the messagefacility explicitly (e.g. in tests). This issue is fixed in art 2.02.02.
Dependent packages¶