The NASA Prognostic Python Packages is a Python framework focused on defining and building models and algorit for prognostics (computation of remaining useful life) of engineering systems, and provides a set of models and algorithms for select components developed within this framework, suitable for use in prognostic applications.
Requirement Text
Allow a user to specify one of several ways that events can trigger an end to a prediction calculation. The ways to implement under this issue are
"all" the prediction calculation will run until all events have occurred (the current method)
"first" the calculation will end when the first event occurs.
In all cases, if the time horizon is reached the prediction calculation will be ended regardless of events. Also the list of events and their states will always be returned to the user.
Background Information
Currently if you specify a list of events to prog_server, the prediction will propagate forward until all the events have been found to be true. If you do not specify any events, the default is to take all events from the model (or all events from all of the sub-models). In either case, if there are events that will never become true, prog_server will continue to run the prediction until the horizon is met, or never stop.
The SWS model is using events for "proximity to threat", and if the craft never approaches a threat, those events will never be true. This would cause the propagation to run forever (or the horizon is met). Also, there are 2 primary events, "trajectory complete" and "end of discharge" for the battery. If the trajectory completes and the craft lands, then "end of discharge" will also never be triggered (or after a very long time). These situations are the rationale for this feature request, it would be nice to end the prediction on the first event reached.
Suggested Solution
None, I will leave solutions to you...
DoD
hm, this default list of tasks looks good - I can't think of more. Maybe not all are required though.
Requirement Text Allow a user to specify one of several ways that events can trigger an end to a prediction calculation. The ways to implement under this issue are
Background Information Currently if you specify a list of events to prog_server, the prediction will propagate forward until all the events have been found to be true. If you do not specify any events, the default is to take all events from the model (or all events from all of the sub-models). In either case, if there are events that will never become true, prog_server will continue to run the prediction until the horizon is met, or never stop.
The SWS model is using events for "proximity to threat", and if the craft never approaches a threat, those events will never be true. This would cause the propagation to run forever (or the horizon is met). Also, there are 2 primary events, "trajectory complete" and "end of discharge" for the battery. If the trajectory completes and the craft lands, then "end of discharge" will also never be triggered (or after a very long time). These situations are the rationale for this feature request, it would be nice to end the prediction on the first event reached.
Suggested Solution None, I will leave solutions to you...
DoD hm, this default list of tasks looks good - I can't think of more. Maybe not all are required though.