DevTreks Preview Production Server URLs (beta 0.8.7, updated January 31, 2012)

Please read the caveats below.

home page:
http://devtreks.cloudapp.net/Home/Index/

typical operations:
http://devtreks.cloudapp.net/agtreks/preview/crops/operationgroup/Weed Management, Nashua corn and beans research plots/324/none 

typical operating budgets:
http://devtreks.cloudapp.net/agtreks/preview/crops/budget/Plot%2001/273071700/none

typical components:
http://devtreks.cloudapp.net/buildtreks/select/commercial/componentgroup/A10 Foundations/42/none 

typical capital budgets:
http://devtreks.cloudapp.net/buildtreks/preview/commercial/investmentgroup/Office Building, 8 story, standard quality -large project-/275505533/none 

typical inputs:
http://devtreks.cloudapp.net/hometreks/preview/farmworkers/inputgroup/Food Nutrition, Dairy Products/2126771715/none 

typical resources:
http://devtreks.cloudapp.net/agtreks/select/agricultura/resourcegroup/Irrigation, Ahuachapan, El Salvador/9/none 

typical stories:
http://devtreks.cloudapp.net/agtreks/preview/agricultura/linkedviewpack/Sistemas de Riego, BASIM Projecto, Ahuachapan, El Salvador/26/none 

typical custom docs:
http://devtreks.cloudapp.net/agtreks/preview/cropsconservation/devpack/Iowa, ARS-NRCS 2, Treatments 1 through 35, Full Set/80/none
 

Caveats

1. The production server is configured for previewing DevTreks (1 web server), not for industrial level work.

2. All of these examples are used when debugging DevTreks. Most debugging focuses on state management, not the quality of the data or 
the accuracy of the calculations. Issues to address as beta testing continues.

3. The new "Save xml/html' button on the edits panel has pros and cons. It significantly reduces the amount of time it takes to 
run some calculations (because the document used in the calculation is prebuilt), but it's easy to forget to click it after edits 
are completed. In addition, it's not a calculated node's parent that needs the save button click action, it's the child node being 
calculated (i.e. the child itself has to be loaded in the edits panel and then the save action taken). On January 31st, a new link, 
Save calculator base doc, was added to the Linked Views panel as another way to address this issue and to fix a bug found with that 
action.

4. Testing data is scattered throughout DevTreks. It will gradually be found and deleted. Most of the 'good data' has not been 
generated using this platform. Less than 1% of calculations and analyses have been run. That means background resources and 
stateful xml and html documents have to be generated anew with notable delays.

5. Although DevTreks hasn't found significant bugs using our conventional testing patterns, it's doubtful that the new cloud 
computing storage code is 100% free of bugs. Time is needed for the code to mature. Bugs that have been discovered in the first full 
day of online testing include some filtered searches, caveat 3 (which as fixed on 1/31), and the display of locals calculator results.

5. Multimedia storage and presentation needs continued improvements.