Comments (5)
Appendix F of the settlements book gives a few examples of uses of the VDISPL program, including their VDIN.dat and VDOU.dat files. Recreating these would be a good start. Furthermore, we could come up with some more inputs ourselves if we see certain options weren't covered in the given test cases, and run them through the original FORTRAN code to get our expected results
from vdisp.
Excellent! Yes, Appendix F sounds great. What we want to have is an argument for completeness. If possible, we want to cover all combinations of the different input options.
I haven't created an issue for requirements yet, but once we document the requirements more system tests will become apparent. I doubt the Settlement book explicitly says the range of expected inputs, but there is an implicit range. The software is written for practical geotechnical problems. This puts limitations on the inputs that we will want to make as explicit as we can. These limitations will give us bounds for additional system tests.
from vdisp.
I have began with some system tests. I first copied down all the example input files from the textbook (there were 4 examples, 1 of which being the input file we already use). Already from trying to parse the first one I found a little mistake in the InputParser module.
from vdisp.
Great! We should have an artifact in our repo that contains this information. Please create a LaTeX document with the title "Verification and Validation Plan." You don't need to worry about organizing it to begin with, just put your system test information in there. (You shouldn't actually copy the contents of the files. You can just put hyperlinks to where they are located.)
Glad to hear that working with the files has helped you debug your code.
from vdisp.
Added document VerifcationAndValidationPlan.pdf in this commit.
from vdisp.
Related Issues (20)
- Credit previous (1994?) code HOT 1
- License
- Add a Citation File HOT 2
- Uninstall instructions
- Adopt a Code of Conduct HOT 1
- User Guide Video
- Code Style Guide
- Acknowledgements HOT 1
- Change displacement graphs to use displacement/H HOT 1
- Units information in the input file HOT 2
- Remove `dir.dat` from version control HOT 2
- Clarify Code base HOT 2
- Update Version and Date-Released in Citation file HOT 1
- Move Custom Exceptions in InputParser to their own module HOT 1
- Separate GUIData from InputData
- Move graphing logic to Graph module
- Rename "OutputFormat" folder to "Output"
- Create a dataflow diagram
- Finish Design.pdf HOT 1
- Get rid of the OutputData struct HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vdisp.