
This example zip should have been unzipped to the folder C:\ where C:\GetOneidaCr\ is created or you will need to reset connections as you encounter connection errors.  Before working with this setup you must have already done full installations of GetRealtime and GetNexrad to your C:\Program Files\ folder for the supporting system files.

Try getting this setup for Snowmelt running before tackling your own runoff points of interest.  Once you do, copy this folder to a new location and start converting setups for your real basin.  

You should download the latest versions of these if newer and just replace the older version in the C:\GetOneidaCr folders and don't worrry about your c:\program files\ because you will never use them:

As of December 20, 2016
1) GetAccess.exe
2) GetRealtime.exe
3) GetGraphs.exe
4) GetNexrad.exe

Setup changes you may need to do.

My Pacific timezone is a -3 hour time shift from New York Eastern so here are ALL the TimeShift change locations you can ever change.

In GetRealtime_setup.txt:
1) Solar Computations Standard Meridian -120 is my Pacific. (not setup for New York)
2) Evapotranspiration Computations Standard Meridian -120. (not setup for New York)
3) FORECAST-NWS time shift of -3 in field 'base1'.

In GetAccess table rsite:
1) ONLY time_shift values of -3 (gage data from another time zone).
Note that computations and radar would normally never have time shifts in rtable if you are in the same time zone as your basin.  Also the USGS gage here always uses Standard Eastern time for some odd reason so you have to deal with that.

There is a time zone table with meridians at the bottom of my web page:

http://getmyrealtime.com/SiteMap.aspx

Once you think you are ready, or even if you think you're not, run GetRealtime.exe 'Start Retrieval' to get the latest data.  After data completion, try 'Select Stations(s)', 'GetGraphs' to admire your results and take it from there.  I would run this example GetRealtime.exe a few times until you get your bearings.  Then try selecting just the radar in batch mode every 30 minutes.  Change a forecast... and only then... call the mayor with your proposals.

Notice that GetRealtime.exe has a setup file to tell it what to do and the GetAccess database table 'rsite' has more info on what is being done by the exe's above.

Look at the file Level2RGB.txt in the GetRealtime.exe folder and note the 62dbz convective cap.  Now look at the GetNexrad.exe foloder's Level2RGB.txt and note the 55dbz hail cap.  Unless your basin is in the southeast you may want to copy the 55dbz cap version to the GetRealtime.exe folder.

Also note how your base flow rises from the out of the box dry condition with each rain event to eventually match the USGS gage flow.  You could uncheck 'Last Run's Storage' to start with wetter conditions and watch the base flow drop to eventually match the USGS gage flow, or try it both ways.  But after the first day remember to recheck the 'Last Run's Storage' checkbox.  This checkbox is only unchecked for startups and should always be checked there after for continuous modeling.  For event modeling it would be unchecked.  The best way to quickly bring your base flow up to speed is the 'Base Flow Adjust' on the 'Scheduled Batch' menu (uncheck Batch after setting).  Try changing the '0.25' precip value to 1.25 and run and compare to the USGS flow and adjust as necessary.  So if your adjusted radar really screws up, you can use this 'Base Flow Adjust' to get things back on track and ready for the next event.  Like wise, you can set the starting snowpack with GetAccess unit value for midnight of the start date (using 5-minute snow comps, else use midnight hour value)

Good Luck and let me know how you do.

Carson@Getmyrealtime.com
