Giter Club home page Giter Club logo

chasm-rhok's People

Watchers

 avatar

chasm-rhok's Issues

Autocomplete Modifies Existing Values

What steps will reproduce the problem?
1. Enter Profile tab
2. Add new segment
3. Enter 12 and 0 for height and length
4. Fill in angle of 90

What is the expected output? What do you see instead?
No values should be modified. Instead, the autocomplete algorithm repopulates 
the length field with 12.

Original issue reported on code.google.com by [email protected] on 17 Nov 2010 at 1:23

Total station interface.

give the ability to load a total station input file.

potential total station inputs vary by brand and manufacturer, however, most 
can import into autocad or microsoft excel.

in both situations, try to get a csv file with column headers in one of two 
formats:

(column x, column y || column eastings, column northings), (height || zed)

then load it up in slope coords in chasm



Original issue reported on code.google.com by [email protected] on 5 Dec 2010 at 2:01

  • Blocked on: #21

Insert "extra" virtual segments

Two additional "virtual" segments need to be created for physical model:

In particular once the user has defined the slope profile, two extra slope 
segments should be added:
• Horizontal segment at end of slope (add segment which is another 15% of the 
user-defined horizontal slope length)
• Vertical boundary at end of slope (add 25% of user-defined slope height)

Original issue reported on code.google.com by [email protected] on 15 Nov 2010 at 3:49

Modify Soil UI to only accept soil properties for "last" layer

Clarification from Liz indicates that interface needs to accept parameters for 
a "last" layer (the bottom) which is underneath everything. No depths need to 
be taken for this "layer" but soil properties are necessary to generate soils 
file.

Interface should always display the soil properties for a "last" layer (even if 
no soil layer has yet been added). As layers are added, this "last" layer 
should slide to the right.

Current workaround is to simply add an extra layer with no soil depths filled 
out. Backend process.php code is hard coded to ignore the last row of soil 
depths for purposes of computation. This hard coded step should be changes once 
UI changes are complete.

Original issue reported on code.google.com by [email protected] on 17 Nov 2010 at 1:12

Change tab order on soil strata page

What steps will reproduce the problem?
1. Add segments to profile
2. Select Soil Tab
3. Select x0
4. Press tab key and field navigates horizontally

What is the expected output? What do you see instead?
Should tab vertically to follow current soil layer


Original issue reported on code.google.com by [email protected] on 15 Nov 2010 at 3:37

Spurious Calculation Errors

Does not always occur.

Seems to be a rounding issue?

Using test case 06 data but with auto populated virtual segments, the number of 
profile columns is one too many and causes PHP die.

Original issue reported on code.google.com by [email protected] on 4 Dec 2010 at 11:39

Firefox display is destroyed

What steps will reproduce the problem?
1.view integratemy.info/chasm-rhok/ in firefox
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.


Original issue reported on code.google.com by [email protected] on 14 Jan 2011 at 12:09

Create boundary conditions file

Need to create boundary conditions file

Awaiting clarification on: detention capacity and max soil evaporation; start 
and stop times; simulated rainfall intensity calculations

Original issue reported on code.google.com by [email protected] on 15 Nov 2010 at 3:45

  • Blocking: #9

Create Stability File

Need to create stability file

Awaiting clarification on: initial radius and increment; stability analysis 
method; method parameters

Original issue reported on code.google.com by [email protected] on 15 Nov 2010 at 3:43

  • Blocking: #9

Remove auto-computed style from Soil Strata parameters when modified by user

What steps will reproduce the problem?
1. Enter Soil tab
2. Choose Soil Type (fields are auto-filled and marked in grey)
3. Change C, phi, or Ks parameter (field remains grey)

What is the expected output? What do you see instead?
Modified fields should no longer be gray

Need to add a change() handler in index.js and a call to 
toggleClass("computed").

Original issue reported on code.google.com by [email protected] on 15 Nov 2010 at 3:32

Implement Export/Import feature to save progress

Possible implementation idea:

1) create save.php which takes the $_REQUEST and "serializes" it to create an 
auto-submitting HTML form pre-populated with hidden fields containing the data 
values

2) modify index.html to have a save button that posts partial data to the 
save.php

3) modify index.html into index.php and pre-process request variables to 
pre-populate form with saved data. Will need to invoke JavaScript functions to 
create new rows.

Original issue reported on code.google.com by [email protected] on 4 Dec 2010 at 1:10

  • Blocking: #25

Create Soils Database file

Need to produce soils database file based on input.

Awaiting clarification of: saturated moisture content; saturated bulk density; 
unsaturated bulk density; soil model computation

Original issue reported on code.google.com by [email protected] on 15 Nov 2010 at 3:40

  • Blocking: #9

Implement Validation Based on More Complete Rules Understanding

Based on clarification from Liz, soil layers can have positive gradients 
meaning soil layers can cross the profile boundary. In addition, soil layers 
can cross each other.

Rules:
<ul>
<li>Soil interfaces can cross each other</li>
<li>When they do so, the upper strata takes precedence over the lower (e.g. in 
the diagram, where strata interface 1, si1, crosses si2, soil 2 is 'lost' and 
the interface below this point is between soil types 1 and 3).</li>
<li>Soil interfaces can cross the slope surface, right hand boundary and x 
axis</li>
<li>soil interfaces can have positive gradients</li>
<li>Water table must have a negative gradient and cross the right hand boundary 
or x axis (not the slope surface)</li>
</ul>

Original issue reported on code.google.com by [email protected] on 18 Nov 2010 at 8:44

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.