Frequently Asked Questions
For general information please see the What is BlueSky? section.
For more technical information, please see the list of Technical documents in the Documentation section.
Please note that these FAQs are under development and new questions are being added. Have a good question or a good answer we should share? Please contact us.
New: The Web Services FAQs have been moved to a separate page.
View: General FAQs | Tool FAQs | Licensing FAQs | Installation FAQs | Running FAQs | Referencing FAQs | BlueSky and other projects FAQs
General FAQs
What's the first thing I should read about BlueSky?
A good place to start is the What is BlueSky? overview section.
What is BlueSky?
BlueSky is a modeling framework. BlueSky modularly links a variety of independent models of fire information, fuel loading, fire consumption, fire emissions, and smoke dispersion.
At each modeling step, BlueSky has several different specific models from which to choose. BlueSky is not a model per se because many different modeling pathways are possible within BlueSky. See the What is BlueSky? section for more information along these lines.
What is a modeling framework?
A modeling framework can be thought of as a system that glues models together, enabling them to pass information to each other, and facilitating the use of multiple models through the same interface.
Is BlueSky a model or not?
Not. BlueSky is a container that other models can function within, but not a model itself. In some ways it is easiest to think of BlueSky as a meta-model (a model of models), but BlueSky does not do any calculations by itself - it relies on the various models it has access to to do to the heavy lifting.
What models are enabled in BlueSky?
Many different fuel loading models, fire consumption models, fire time profile models, fire emissions models, plume rise models, trajectory models, and dispersion models are enabled directly within BlueSky. A complete list is in the Modules section.
Additionally, BlueSky can write information out to very standard output formats like csv that many other models and tools can then use. In this way BlueSky can help enable cross communication between the models directly enabled by it and outside models. See Import and Export Functionality for more information.
Where is BlueSky used?
BlueSky is used in a variety of ways including pure science projects, decision-support-systems, operational forecasting and more. We have tried to gather the list in the BlueSky in Action section. Let us know if your project isn't listed and we'll add it!
Where can I see BlueSky-enabled predictions?
There are many sites that have BlueSky-enabled predictions. A list with links can be found in the BlueSky in Action section under Daily Fire and Smoke Predictions. Many of the experimental prediction systems can also be accessed through a unified Google Earth folder structure found here.
What BlueSky-enabled tools are available for .... FAQs
... planning a burn?
The Air Quality Impact Planning Tool (AQUIPT) and the BlueSky Interactive Fire Scenario (IFS) application both utilize longer term climatologies of weather data, and both can take user-input fire information. AQUIPT will provide probablistic forecasts of smoke based on numerous individual model runs during the season of interest in a batch mode, while BlueSky IFS does single runs in real-time. See the management tools page.
... deciding to light a burn?
Information on potential smoke impacts can be obtained by running smoke model predictions for the burn plan. This can be done in real-time for a single fire through the BlueSky Interactive Fire Scenario (IFS) application. Prescribed burn reporting systems are also automatically integrated into some smoke model predictions. Currently the FCAMMS PNW run uses information from the RAZU, ODF, WA DNR, and other Rx systems around the northwest. Additionally Rx burn information can be included manually into the FCAMMS National and CANSAC runs by contacting those groups directly. See the daily fire information and smoke predictions page.
... managing a fire?
Daily smoke predictions are available from a number of sources. Some of these systems (FCAMMS, CANSAC) offer mechanisms to allow incident command teams the ability to adjust projected fire size. The BlueSky team is also working with the Wildland Fire Decision Support System (WFDSS) to develop tools using BlueSky to be incorporated and accessed directly within WFDSS. Additionally, fire scenarios can be interactively run through the BlueSky Interactive Fire Scenario (IFS) tool.
... managing an airshed?
Airshed air quality preditions from all the burns in a region can be obtained from most of the daily smoke model runs listed in the daily fire information and smoke predictions page. Under special circumstances the prototype Emergency Smoke Response System may also be active and producing model predictions.
... evaluating NAAQS exceedances?
This is an active area of work. The BlueSky team is in contact with WESTAR as they work through how to document exceptional events. It is clear that some of the daily model runs, such as the STI Gateway runs that are done both with and without fire, have value to documenting NAAQS exceedances. Please contact us to learn more.
Licensing Agreement FAQs
Can I distribute BlueSky?
Not directly, no. BlueSky is freely distributed from this site under a modified Modified GPL License Agreement which is agreed to by all users of BlueSky. As stated in the agreement, please send other users here to get their copy of BlueSky. Don't worry, it's free. It's just that centralizing distribution enables us to ensure that everyone is getting the most current version, and to track where BlueSky is used so that we can retain funding to bring you the next version of BlueSky. If you have developed something new for BlueSky please send it back to us so that everyone can benefit. In this way BlueSky can continue to grow as a collaborate effort.
I've made a new module. Now what?
Send it to us! We'd love to get the module and to incorporate it into the BlueSky source repository for distribution to the broader BlueSky community. Don't worry, your module inherets the BlueSky License Agreement which ensures that it and any modifications to it remain free and open-sourced for the larger communities use.
Installing BlueSky FAQs
What is needed to run BlueSky?
Please see the Technical Requirements page.
How do I obtain BlueSky?
Please see the Downloading and Installing page.
How do I install BlueSky?
Please see the Downloading and Installing page.
Running BlueSky FAQs
Is BlueSky easy to use?
Yes. We have worked hard to make BlueSky as easy as possible to use. In many cases it is significantly easier to use than the original models. BlueSky is vastly easier that trying to run the original models in combination. Still, BlueSky is a complex system, containing all of the complexities of the underlying models, and should only be run by users willing to tackle this complexity.
What is the BlueSky web-services/service-oriented architecture?
BlueSky is utilizing the standard web-services idea. We run a server which responds to internet calls via an XML standard and runs any module within the framework. Please see the Running BlueSky through web-services page for more information.
What kinds of input are needed to run BlueSky?
It depends on whether you are running BlueSky locally (on your servers) or remotely (on our servers) through the web-service architecture. Please see the What data do I need? section.
I have my own model input ... can I use it with BlueSky?
Yes. BlueSky uses simple, standard format files, mostly in ASCII comma separated value (CSV) format, that are creatable by many programs. If your model does not use this format directly, usually it is easy to write a simple script to convert your model's output for use.
How do I run BlueSky locally?
Please see the Running BlueSky locally page.
How do I run CMAQ with BlueSky?
BlueSky can create S.M.O.K.E. emissions preprocessor ready files. Please see the S.M.O.K.E.-ready output page.
What does my error mean?
Please see the Understanding an error page.
Referencing BlueSky FAQs
How do I reference BlueSky?
Please see the How to reference BlueSky page.
BlueSky and other projects FAQs
What is SMARTFIRE?
SMARTFIRE is a fire information system that integrates information from multiple fire detection and reporting systems, reconciling them into a single data stream. SMARTFIRE currently utilizes the NOAA Hazard Mapping System satellite fire detects and the Incident Command System (ICS) 209 ground reports for its daily fire information stream. See the SMARTFIRE page for more information.
How are BlueSky and SMARTFIRE related?
BlueSky and SMARTFIRE are software "siblings" that are designed to work well together. BlueSky knows how to retrieve SMARTFIRE fire information off of the SMARTFIRE servers automatically. See the SMARTFIRE page for more information.
What is SEMIP?
SEMIP is the Smoke and Emissions Model Intercomparison Project, a Joint Fire Science Project funded project detailed at http://semip.org. SEMIP is designed to be a collaborative, open-architecture intercomparison project that compares fire information systems, fuel loading maps, fire consumption models, fire emissions models, plume rise models, and dispersion models, both separately and in combination.
How are BlueSky and SEMIP related?
BlueSky and SEMIP are only related in that, for convenience, the first phases of SEMIP are utilizing some of the functionality provided by BlueSky. However, SEMIP is not limited to models that are enabled in BlueSky, and SEMIP is not BlueSky-specific. Similarly, BlueSky provides other functionalities that have no relationship with SEMIP.
How does BlueSky relate to the National Weather Service's smoke forecasts?
The U.S. National Weather Service's operation smoke forecasts currently utilize a earlier version of BlueSky to compute fire emissions. Work is underway to evaluate the newest version of BlueSky (v3.1) for use by the next version of the NWS smoke forecasting system.
How does SMARTFIRE/BlueSky relate to the U.S. EPA's National Emissions Inventory?
SMARTFIRE/BlueSky has been used to create, on an evaluation basis, fire emissions for the U.S. National Emissions Inventory for years 2003-2006. These emissions were then compared with other NEI fire emissions created using other methodologies. Based on the results of this analysis SMARTFIRE/BlueSky has been identified in draft guidance produced by the EPA for use in the 2008 NEI.
How does BlueSky/SMARTFIRE relate to the WRAP's Fire Emissions Tracking System (FETS)?
The BlueSky Team is working with the developers of the Fire Emissions Tracking System (FETS) - specifically the WRAP and AirSciences - to enable the ease use of FETS data within BlueSky, including automatically retreiving FETS data and integration of FETS and SMARTFIRE functionalities. This is an active project. Please watch this site for more information.
Future of BlueSky FAQs
Where is BlueSky headed?
BlueSky is continuing to add more models and to refine the process for getting from fire information to smoke. BlueSky splitting out several new modeling steps - specifically "Local Weather" and "Fuel Moisture" - and adding new types of emissions calcuation streams - specifically radiative fire power satellite emissions. BlueSky is also linking with other modeling systems and tools now under developement - such as the Wildland Fire Decision Support System (WFDSS), the Fire Emissions Tracking System (FETS), the Interagency Fuels Treatment Decision Support System (IFT-DSS), and the Fire Fuels Application (FFA) - in order to make importing and exporting BlueSky enabled information easier and more useful. See the white paper in the Documents section for more information.
What modules will be added?
Under a new NASA grant we will be adding satellite-based fuel moistures, and splitting fuel moisture calculations into their own modeling step. We will also be adding the FLAMBE emissions model. A Local Weather modeling step will also be added to facilitate the use of weather station data.
What modules would you like to add?
We would like to add even more satellite information based modules, including radiative-fire-power emissions models. In particular we would like to add Weidinmyer's satellite-based emissions calculation system. We are working with Christine Weidinmyer to enable this.
We would like to add prescribed burn information, particularly from the Fire Emissions Tracking System (FETS). We believe that this information should ideally be joined with the information currently in the SMARTFIRE system so a unified data stream can be created. We are working with AirSciences and the WRAP to enable this.
We would like to add modules to encompass agricultural and rangeland burning. We are in discussion with Washington State University's ClearSky system to try to enable this.
What about agricultural and rangeland burning?
Currently BlueSky does not handle agricultural or rangeland burning. Efforts are underway to create an alternate emissions pathway within BlueSky, similar to Washington State University's ClearSky emissions pathway, that would be able to compute both agricultural and rangeland burning emissions.
