Proposed: a "status table" or "dashboard" composed of an aggregated JSON file that contains go/no-go and, where practical, at least a category of failure, for each subcomponent of the project. Thus, if the forecast map fails but everything else is obtained okay, the table would be mostly "green", with perhaps an indicator marker of "yellow", indicating the user might want to see what has gone wrong.
Individual subsystems could put their diagnostic data into the standard JSON output, that could then be collected by a new class, and served up as a discrete JSON API endpoint using Flask, as most of the data is already served up that way.
Proposed: a "status table" or "dashboard" composed of an aggregated JSON file that contains go/no-go and, where practical, at least a category of failure, for each subcomponent of the project. Thus, if the forecast map fails but everything else is obtained okay, the table would be mostly "green", with perhaps an indicator marker of "yellow", indicating the user might want to see what has gone wrong.
Individual subsystems could put their diagnostic data into the standard JSON output, that could then be collected by a new class, and served up as a discrete JSON API endpoint using Flask, as most of the data is already served up that way.