RAVEN is a flexible and multi-purpose probabilistic risk analysis, validation and uncertainty quantification, parameter optimization, model reduction and data knowledge-discovering framework.
Is your feature request related to a problem? Please describe.
The TSA module applies algorithms at the segment ("local") level. If a user wants to apply the algorithms to the full signal instead ("globally"), then the <Segment> node in the XML should be omitted. However, there is no option to mix global and local applications of algorithms.
Describe the solution you'd like
It would be nice to distinguish algorithms applied globally and locally in the XML script. Detrending the full signal rather than on a per-segment basis could sometimes work better. E.g., detrending Fourier modes with periods longer than the segment length would be best to do on the global signal. Users can still train, for example, ARMA models on each segment.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.
[x] 1. Is it tagged with a type: defect or task?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)
For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.
[x] 1. If the issue is a defect, is the defect fixed?
[x] 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
dylanjm
commented
1 year ago
Issue Description
Is your feature request related to a problem? Please describe. The TSA module applies algorithms at the segment ("local") level. If a user wants to apply the algorithms to the full signal instead ("globally"), then the
<Segment>node in the XML should be omitted. However, there is no option to mix global and local applications of algorithms.Describe the solution you'd like It would be nice to distinguish algorithms applied globally and locally in the XML script. Detrending the full signal rather than on a per-segment basis could sometimes work better. E.g., detrending Fourier modes with periods longer than the segment length would be best to do on the global signal. Users can still train, for example, ARMA models on each segment.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.
For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.