Simulation: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
= Simulation and Engineering Software = | = Simulation and Engineering Software = | ||
== Scenarios == | |||
Imagine you built a simulator so that when you added weight to the climber, the ribbon dimensions got bigger. If a spreadsheet created calculations that boiled down to simple algebraic formulas, those could be put into a video game. If someone improves the spreadsheet, they can swap in a different algebraic constant. | |||
== Physics Models == | |||
We believe that http://www.ode.org could be a good simulation engine for realtime, or non-realtime calculations. | |||
Here is an excellent summary document: http://keithcu.com/cgi-bin/hg.cgi?raw-file/073cec0e2635/docs/dynamics.pdf | |||
More: [[Codebase_Analysis#Physics_Engines]] | |||
== | ''Dynamics, basic principles relationships, materials properties.'' | ||
== Finite Element Analysis == | |||
(''Can someone please analyze this FEniCS project?'') | |||
http://www.fenics.org/wiki/FEniCS_Project | |||
Complete list [http://en.wikipedia.org/wiki/List_of_finite_element_software_packages] | |||
== Spreadsheets == | |||
A Spreadsheet is a monster tool, but the various pieces need to be linked or otherwise integrated. Just think how many places a spreadsheet cost calculator must go to come up with a "final" number! Spreadsheets get very cool when you start to combine the data from various pieces together. Every separate spreadsheet is a locked up silo of information, unless it is linking to other ones. We have 16 spreadsheets in our archives, and that number already is too big. If you were to build a finite element analysis engine inside a spreadsheet, I would suggest that be a separate one! | |||
It is possible to have our models and simulations be huge and easy to approach. You just organize the data into Sheets, Create headings, make important boxes be highlighted, etc. | |||
''Ribbon dimensions, performance trade-offs, overall interactions matrix.'' | |||
== Collaboration == | |||
OpenOffice has the ability to merge of documents, and to do change tracking, and there other solutions, because underlying the OpenOffice document is a bunch of textual XML which can easily be merged and diffed. As more people start working on documents at the same time, we can find what works best. | |||
In general it should not be a problem: | |||
People can read an (old version) of a binary document all they want, and if they want to edit it, they should make sure they have the latest copy, make changes, and then upload them right away. The idea that our spreadsheets will be so busy that there will be merge conflicts is very optimistic! | |||
== | We could try various things like GoogleDocs for spreadsheet collaboration, but we throw away like 90% of our features! | ||
== Collada == | |||
We will use the Collada format which is open, XML, has 3-D and physics capabilities. | We will use the Collada format which is open, XML, has 3-D and physics capabilities. | ||
Collada introduction: http://keithcu.com/cgi-bin/hg.cgi?raw-file/6bcb243bfc7d/docs/COLLADA.odp | Collada introduction: http://keithcu.com/cgi-bin/hg.cgi?raw-file/6bcb243bfc7d/docs/COLLADA.odp | ||
== Blender == | == Blender == | ||
People complain that it is a little hard to get into, but extremely powerful and it has some physics simulation capabilities built in and supports Collada. | |||
Complete tutorial: http://www.cdschools.org/54223045235521/lib/54223045235521/BlenderBasics2.42a.pdf | |||
Complete tutorial: [http://www.cdschools.org/54223045235521/lib/54223045235521/BlenderBasics2.42a.pdf] | |||
http://www.blender.org/education-help/tutorials/tutorial-folder/blender-user-interface-tutorial/ | UI Intro: [http://www.blender.org/education-help/tutorials/tutorial-folder/blender-user-interface-tutorial/] | ||
http://www.blender.org/education-help/tutorials/#c836 | Various tutorials: [http://www.blender.org/education-help/tutorials/#c836] | ||
http://en.wikibooks.org/wiki/Blender_3D:_Noob_to_Pro | Wikibook: [http://en.wikibooks.org/wiki/Blender_3D:_Noob_to_Pro] | ||
== Other Software == | == Other Software == | ||
NASA's free code: http://opensource.arc.nasa.gov/ | NASA's free code: http://opensource.arc.nasa.gov/ | ||
Matlab-type: | Matlab-type: | ||
http://en.wikipedia.org/wiki/GNU_Octave | http://en.wikipedia.org/wiki/GNU_Octave | ||
Revision as of 09:47, 7 July 2008
Simulation and Engineering Software
Scenarios
Imagine you built a simulator so that when you added weight to the climber, the ribbon dimensions got bigger. If a spreadsheet created calculations that boiled down to simple algebraic formulas, those could be put into a video game. If someone improves the spreadsheet, they can swap in a different algebraic constant.
Physics Models
We believe that http://www.ode.org could be a good simulation engine for realtime, or non-realtime calculations. Here is an excellent summary document: http://keithcu.com/cgi-bin/hg.cgi?raw-file/073cec0e2635/docs/dynamics.pdf More: Codebase_Analysis#Physics_Engines
Dynamics, basic principles relationships, materials properties.
Finite Element Analysis
(Can someone please analyze this FEniCS project?) http://www.fenics.org/wiki/FEniCS_Project
Complete list [1]
Spreadsheets
A Spreadsheet is a monster tool, but the various pieces need to be linked or otherwise integrated. Just think how many places a spreadsheet cost calculator must go to come up with a "final" number! Spreadsheets get very cool when you start to combine the data from various pieces together. Every separate spreadsheet is a locked up silo of information, unless it is linking to other ones. We have 16 spreadsheets in our archives, and that number already is too big. If you were to build a finite element analysis engine inside a spreadsheet, I would suggest that be a separate one! It is possible to have our models and simulations be huge and easy to approach. You just organize the data into Sheets, Create headings, make important boxes be highlighted, etc.
Ribbon dimensions, performance trade-offs, overall interactions matrix.
Collaboration
OpenOffice has the ability to merge of documents, and to do change tracking, and there other solutions, because underlying the OpenOffice document is a bunch of textual XML which can easily be merged and diffed. As more people start working on documents at the same time, we can find what works best.
In general it should not be a problem: People can read an (old version) of a binary document all they want, and if they want to edit it, they should make sure they have the latest copy, make changes, and then upload them right away. The idea that our spreadsheets will be so busy that there will be merge conflicts is very optimistic!
We could try various things like GoogleDocs for spreadsheet collaboration, but we throw away like 90% of our features!
Collada
We will use the Collada format which is open, XML, has 3-D and physics capabilities. Collada introduction: http://keithcu.com/cgi-bin/hg.cgi?raw-file/6bcb243bfc7d/docs/COLLADA.odp
Blender
People complain that it is a little hard to get into, but extremely powerful and it has some physics simulation capabilities built in and supports Collada.
Complete tutorial: [2]
UI Intro: [3]
Various tutorials: [4]
Wikibook: [5]
Other Software
NASA's free code: http://opensource.arc.nasa.gov/
Matlab-type: http://en.wikipedia.org/wiki/GNU_Octave
