Skip to main content
ARS Home » Southeast Area » Oxford, Mississippi » National Sedimentation Laboratory » Watershed Physical Processes Research » Docs » How to Obtain the SIDO Documentation and Software

How to Obtain the SIDO Documentation and Software
headline bar

The NSL Technical Report No. 5, the SIDO source code, executable code, and all test files can be downloaded from this website.

To download the SIDO files:

1. Click link: SIDO
2. Select the file to be downloaded by placing the cursor on the filename. Click the right mouse button.
3. Place the cursor on the SAVE AS type statement. Click left mouse button and follow instructions for saving the file.
4. Repeat steps 2 and 3 as needed. For other browsers follow similar type commands.

Directory of C:\SIDO

DOCUMENTATION Contains the complete set of documentation for SIDO in pdf format, and the read-only version of Acrobat Reader Version 3.0 software (AR32E30.EXE) that must be executed to install. This software should be used to read the pdf documents. EXECUTABLE Contains the 1996 release version of the executable file for SIDO.SOURCE_CODE Contains all the source code (standard ANSI Fortran 90) for SIDO. The Sediment Intrusion & Dissolved Oxygen (SIDO) computer model was written in standard ANSI Fortran 90 code (American National Standard Programming Language Fortran, ANSI X3.198-1992 and International Standards Organization, ISO/IEC 1539: 1991, Information technology--Programming languages--Fortran) without any non-standard enhancements. It was developed using Microsoft's Fortran PowerStation version 4.0 with the its companion Developer Studio under Windows 95. Short and long file names were used. VERIFICATION_DATA contains all the alpha test verification files as well as the files used to generate the data for the tables and figures used in the documentation. The batch files will copy the test data to the necessary generic-name input files, execute SIDO to generate the generic-name output file, copy the output file to a file with a name associated with the specific test, and then delete the generic-name output file.