-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added the capability to specify time interval and removed function to… #1830
Conversation
… postprocess more than one feature and target set per step
Uploading required test files that were not addable during local branch merging.
Job Mingw Test on 95a2587 : invalidated by @yoshiurr-INL Random issue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like to keep the capacities to compute multiple feature-target pairs in the single post-processors. @yoshiurr-INL Please let me know what do you think.
I considered reenabling the multiple feature-target pairs but realized this would essentially require the user to create multiple DataObjects and OutStreams anyway due to potentially using different pivot parameters depending on how many data points is provided from the feature and target. If we recall, 'pivotParameterFeature' and 'pivotParameterTarget' are utilized for this postprocessor. If the grids are nonuniform, it is possible for one transient to use 'pivotParameterFeature' and for another transient to use 'pivotParameterTarget' due to the auto-selection algorithm implemented to choose coarser grids and have the finer data interpolate/extrapolate. Then, the pivot parameter for the output DataObject cannot be described using a single pivot parameter. To avoid this risk, I propose to keep the current changes. For the suggestion to add an attribute to provide the user the choice to use ratio or raw time values, I agree that should be an option and will make changes ASAP. |
The capability to use ratios and raw values is now available. |
Job Test qsubs sawtooth on 7c94021 : invalidated by @yoshiurr-INL Restart Sawtooth tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yoshiurr-INL I have some comments for your consideration.
Job Test qsubs sawtooth on d444b2f : invalidated by @yoshiurr-INL Restart Sawtooth tests |
2 similar comments
Job Test qsubs sawtooth on d444b2f : invalidated by @yoshiurr-INL Restart Sawtooth tests |
Job Test qsubs sawtooth on d444b2f : invalidated by @yoshiurr-INL Restart Sawtooth tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have some minor comments for you to consider.
it will output an error. | ||
\item \xmlNode{Targets}, \xmlDesc{comma separated string, required field}, specifies the names of the targets. Make sure the feature data are normalized by a nominal value. \nb Each target is paired with a feature listed in xml node \xmlNode{Features}. | ||
To enable user defined time interval selection, this postprocessor will only consider the first feature name provided. If user provides more than one, | ||
itt will output an error. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
itt --> it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
\item \xmlNode{Options} | ||
\begin{itemize} | ||
\item \xmlNode{pivotParameter} | ||
\end{itemize} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you need these lines?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do not need these. Deleted.
separateFeatureDataInput.addParam("type", InputTypes.StringType, descr="""Specifies what type of user defined time intervals have been selected from | ||
the feature pivot parameter. Options are currently `ratio' or `raw_values'""") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's use raw string descr = r""" .... """
, and change "raw_values" --> raw\_values
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed.
separateTargetDataInput.addParam("type", InputTypes.StringType, descr="""Specifies what type of user defined time intervals have been selected from | ||
the target pivot parameter. Options are currently `ratio' or `raw_values'""") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
similar to above comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed.
Job Test qsubs sawtooth on 08e843a : invalidated by @yoshiurr-INL Restart Sawtooth tests |
Job Test qsubs sawtooth on 08e843a : invalidated by @wangcj05 |
PR checklist is satisfied. |
… postprocess more than one feature and target set per step
Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
close #1829
What are the significant changes in functionality due to this change request?
Allows users to specify time intervals in ratio terms of the full time interval (pivot parameter). To prevent confusion, the capability to postprocess multiple pairs of features and targets in one single step has been deprecated. To postprocess multiple time intervals, the user will now have to create a new step and add it to the sequence.
For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.
<internalParallel>
to True.raven/tests/framework/user_guide
andraven/docs/workshop
) have been changed, the associated documentation must be reviewed and assured the text matches the example.