-
Notifications
You must be signed in to change notification settings - Fork 121
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Adding test files per process for histmaker
- Loading branch information
Showing
6 changed files
with
181 additions
and
163 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,34 +1,34 @@ | ||
.\" Manpage for fccanalysis-file | ||
.\" Manpage for fccanalysis-script | ||
.\" Contact [email protected] to correct errors or typos. | ||
.TH FCCANALYSIS\-FILE 7 "15 Aug 2023" "0.7.0" "fccanalysis-file man page" | ||
.TH FCCANALYSIS\-SCRIPT 7 "26 Oct 2023" "0.7.0" "fccanalysis-script man page" | ||
.SH NAME | ||
fccanalysis\-file \- analysis file specification | ||
fccanalysis\-script \- analysis script specification | ||
.SH SYNOPSIS | ||
.sp | ||
* | ||
.sp | ||
.SH DESCRIPTION | ||
The analysis file is expected to be a valid Python script containing either | ||
part of or the full analysis. There are two basic modes how to run a FCC | ||
The analysis script is expected to be a valid Python script containing either | ||
part of or the full analysis. There are two basic modes how to run the FCC | ||
analysis, one is to run in the managed mode like so: | ||
.PP | ||
.RS 4 | ||
fcc run <analysis_file.py> | ||
fcc run <analysis_script.py> | ||
.RE | ||
.PP | ||
or | ||
.PP | ||
.RS 4 | ||
fcc final <analysis_file.py> | ||
fcc final <analysis_script.py> | ||
.RE | ||
.PP | ||
where user needs to provide minimal number of variables and settings. In this | ||
mode the RDataFrame is managed for the user and it can be controlled by defining | ||
several global attributes in the analysis file. The other mode is to run the | ||
analysis file as regular python script: | ||
several global attributes in the analysis script. The other mode is to run the | ||
analysis script as regular python script: | ||
.PP | ||
.RS 4 | ||
python <analysis_file.py> | ||
python <analysis_script.py> | ||
.RE | ||
.PP | ||
here user has full control over the RDataFrame, but has to create all necessary | ||
|
@@ -47,7 +47,7 @@ indicated in the $FCCDICTSDIR environment variable. | |
.PP | ||
\fBprodTag\fR | ||
.RS 4 | ||
Provides information where to find input files. There are several way how to | ||
Provides information where to find input files. There are several ways how to | ||
find the information, one of them uses YAML file which is being searched for in | ||
the subfolders of $FCCDICTSDIR. | ||
.RE | ||
|
@@ -78,6 +78,13 @@ The analysis RDataFrame can be split into several chunks\&. | |
.br | ||
Default value: 1 | ||
.RE | ||
\fItestfile\fR | ||
.RS 4 | ||
Specifies the test file which can be used in test mode, see | ||
fccanalysis-run(1)\&. | ||
.br | ||
Default value: None | ||
.RE | ||
.RE | ||
.PP | ||
\fBoutputDir\fR | ||
|
@@ -105,7 +112,7 @@ Default value: False | |
.PP | ||
This section is under construction. You are invited to help :) | ||
.SH SEE ALSO | ||
fccanalysis(1), fccanalysis-run(1) | ||
fccanalysis(1), \fBfccanalysis-run\fR(1) | ||
.SH BUGS | ||
Many | ||
.SH AUTHORS | ||
|
Oops, something went wrong.