ALE Driver Architecture

[jrcain-usgs]

Licensing

This project is mostly composed of free and unencumbered software released into the public domain, and we are unlikely to accept contributions that are not also released into the public domain. Somewhere near the top of each file should have these words:

This work is free and unencumbered software released into the public domain. In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain.

• I dedicate any and all copyright interest in this software to the public domain. I make this dedication for the benefit of the public at large and to the detriment of my heirs and successors. I intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

Addresses the conceptual points in #32

[Kelvinrr]

This needs to cover how loads works. That is, how it iterates over each driver and attempts to build an ISD with each. How loads quick rejects ISDs (using instrument IDs, look at the code and instructions for how to make an ale driver for examples). And how this can sometimes cause issues (sometimes a driver can succeed before the driver you want).

Also mention isd_generate as an app that can do most of the boilerplate for you.

[jrcain-usgs]

sometimes a driver can succeed before the driver you want

I mentioned this in my current draft, but I don't think I've seen this issue myself. Would different instrument_ids prevent this from happening? What can someone do if that happens to them?

[acpaquette]

Overall good encapsulation of the ALE architecture, couple things to address when talking about ISIS cameras

[Kelvinrr]

My concerns have been addressed, if @acpaquette also gives a +1 then this is good to merge.