Enhancement Request: Species <-> Networks and Error Handling

[zacadelman]

Enhancement Request: Species <-> Networks and Error Handling

[wkappel]

I'd hate to hard code a list of available species for each network into the AMET code since network species availability does change from time to time. I could put a check in that if a query for a species returns all null values that AMET reports a message like "No data found for [species] from [network] network. It may be that [network] does not observe [species] or no data are available for your query specifications." Now, there are obviously other reasons why there may be no data for a particular query, but at least this would report that no data were found and let the user figure out why. There is a list of species per network in the User's Guide. I could refer users to that guide as well.

What do you think?

[wkappel]

To this end, I've updated the scripts that handle multiple networks to avoid crashing if a network returns an empty query. Previously the scripts would crash if any query returned no results. Now, the script will attempt to continue on to the next network if an empty result is returned. This should make a number of the scripts more robust. If all the queries return no results, the script still crashes however. These updates will be available in the AMETv1.4 release.