|
187 | 187 | "cell_type": "markdown", |
188 | 188 | "metadata": {}, |
189 | 189 | "source": [ |
190 | | - "In the first section we introduced simulating to a set time. For most applications, users are not interested in the system evolution over a certain timeperiod, but instead in simulating to some event of interest.\n", |
| 190 | + "In the first section we introduced simulating to a set time. For most applications, users are not interested in the system evolution over a certain time period, but instead in simulating to some event of interest.\n", |
191 | 191 | "\n", |
192 | 192 | "In this section we will introduce the concept of simulating until an event occurs. This section builds upon the concepts introduced in the previous section.\n", |
193 | 193 | "\n", |
|
208 | 208 | "cell_type": "markdown", |
209 | 209 | "metadata": {}, |
210 | 210 | "source": [ |
211 | | - "If you recall, the ThrownObject model is of an object thrown into the air. The model has two events, `impact` and `falling`. In a real prognostic models, these events will likely correspond with some failure, fault, or warning threshold. That said, events can be any event of interest that a user would like to predict. \n", |
| 211 | + "If you recall, the ThrownObject model is of an object thrown into the air. The model has two events, `impact` and `falling`. In real prognostic models, these events will likely correspond with some failure, fault, or warning threshold. That said, events can be any event of interest that a user would like to predict. \n", |
212 | 212 | "\n", |
213 | 213 | "Now let's repeat the simulation from the previous example, this time simulating until an event has occured by using the [`simulate_to_threshold`](https://nasa.github.io/progpy/api_ref/prog_models/PrognosticModel.html#prog_models.PrognosticsModel.simulate_to_threshold) method." |
214 | 214 | ] |
|
235 | 235 | "cell_type": "markdown", |
236 | 236 | "metadata": {}, |
237 | 237 | "source": [ |
238 | | - "By default, `simulate_to_threshold` simulates until the first event occurs. In this case, that's `falling` (i.e., when the object begins falling). For this model `falling` will always occur before `impact`, but for many models you wont have such a strict ordering of events. \n", |
| 238 | + "By default, `simulate_to_threshold` simulates until the first event occurs. In this case, that's `falling` (i.e., when the object begins falling). For this model `falling` will always occur before `impact`, but for many models you won't have such a strict ordering of events. \n", |
239 | 239 | "\n", |
240 | | - "For users interested in when a specific event is reached, you can indicate that using the `threshold_keys` argument. For example," |
| 240 | + "For users interested in when a specific event is reached, you can indicate which event(s) you'd like to simulate to using the `threshold_keys` argument. For example," |
241 | 241 | ] |
242 | 242 | }, |
243 | 243 | { |
|
0 commit comments