rescale_forecast
Rescale prediction data from the NormalizedForecaster agent to a specific min and max range required for your use case. Use this tool when converting normalized values (0 to 1) into meaningful units or levels, ensuring accuracy in forecasting outputs.
Instructions
A tool that rescales the prediction data (values between 0 and 1) from the NormalizedForecaster agent to scale required for a use case
When to use this tool:
- Use this tool when there is enough information from the user or use cases to determine a reasonable min and max for the forecast predictions
- Do not attempt to rescale or denormalize the predictions on your own without using this tool.
- Also, if the best min and max for the use case is 0 and 1, then no rescaling is needed since that is already the scale of the predictions.
- If a user requests to convert from probabilities to a unit in levels, be sure to caveat your use of this tool by noting that probabilities do not always scale uniformly to levels. Rescaling can be used as a rough first-pass estimate. But for best results, it would be better to start a new Chronulus forecasting use case predicting in levels from the start.
How to use this tool:
- To use this tool present prediction_id from the normalized prediction and the min and max as floats
- If the user is also changing units, consider if the units will be inverted and set the inverse scale to True if needed.
- When plotting the rescaled predictions, use a Rechart time series plot with the appropriate axes labeled and include the chronulus prediction explanation as a caption below the plot.
- If you would like to add additional notes about the scaled series, put these below the original prediction explanation.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| invert_scale | No | Set this flag to true if the scale of the new units will run in the opposite direction from the inputs. | |
| prediction_id | Yes | The prediction_id from a prediction result | |
| y_max | Yes | The expected largest value for the use case. E.g., for product sales, 0 would be the largest possible value would be given by the user or determined from this history of sales for the product in question or a similar product. | |
| y_min | Yes | The expected smallest value for the use case. E.g., for product sales, 0 would be the least possible value for sales. |