The WINGSPAN/MFIT software is being distributed as-is, with no express or implied guarantees of its performance. We have striven to make the software as error-free as we could. We expect that bugs will show up, so we have formulated a method to deal with them which won't strain our limited programming resources to the breaking point. First, if you get stuck somewhere and don't know what to do, please read this entire document or refer to the on-line help files, which can be brought up by clicking the HELP button on WINGSPAN's main menu. There are some things you must know before you can use WINGSPAN effortlessly and effectively. Next, if you have questions the documentation doesn't seem to answer, or if you find a true bug, contact Jerry Bonnell at the GROSSC (email: GROSSC::BONNELL). A true bug is defined as one that is reproducible when the original, unmodified software is run. A bug report must be accompanied by a screen shot of all the error lines reported by IDL, as well as a brief description of how the error was obtained, including the BFITS and lookup files, if appropriate. Incomplete bug reports will be returned to the user by the GROSSC for more information.
Errors in user-modified routines cannot be fixed by us. You will be asked by the GROSSC whether you have verified that the error exists in the original, distribution software. We request that any user who wishes to make a modification to the program also change the version information, which is defined in the file wingspan/idl_source/wgsp_version.dat. Uniquely identify the modified version (we suggest adding the programmer's or host institution's initials to the end of the version string).
![[image 4K]](/icons-local/batse_icon.gif){kind=icon}
BATSE Home Page