Difference between revisions of "User:Al Da Best/devlog"
From BRL-CAD
Al Da Best (talk | contribs) (Added Development Log page) |
Al Da Best (talk | contribs) (Added dev schedule to devlog page) |
||
| Line 23: | Line 23: | ||
8th : Updated Wiki pages | 8th : Updated Wiki pages | ||
| + | |||
| + | |||
| + | |||
| + | ===Development Schedule=== | ||
| + | |||
| + | (Unless otherwise specified, 40+ hours of work to be assumed): | ||
| + | |||
| + | 23rd April – 5th May | ||
| + | * Flesh out any last details in project, have all objectives clear and the schedule complete. | ||
| + | * Gain commit access before or during this point | ||
| + | 5th May – 21st May | ||
| + | * Learn as much about any relevant libraries such as Bullet, and BRL-CAD libraries such as librt and libged as I can, to enable me to be able to get straight into coding with the knowledge of what is already there and how to use it. | ||
| + | * Start writing function outlines, header files to make it clearer as to what goes where and how to reuse code efficiently. | ||
| + | * Iron out any current bugs in the simulation files, to ensure a fully working simulation environment. | ||
| + | 21st May – 28th May | ||
| + | * Coding begins. Start by working on the gravitational system as this will be the easiest to implement and so will take the shortest amount of time, and will make sure I am completely familiar with the code. | ||
| + | 28th May – 4th June | ||
| + | * Milestone 1: Gravitational system complete and fully bug tested. | ||
| + | * Once milestone 1 is reached, begin work on the fluid system, starting with functions to calculate drag on surfaces | ||
| + | 4th June – 11th June | ||
| + | * Exam period starts at University, limited time available. | ||
| + | * In available time, work on drag functions and start to implement functions to resolve the forces from the drag (In x,y and z directions) | ||
| + | 11th June – 18th June | ||
| + | * Exam period ends | ||
| + | * Carry on implementing functions to resolve forces and start on functions to resolve moment forces to show rotation in the simulation | ||
| + | 18th June – 25th June | ||
| + | * Continue working on the fluid system and begin bug testing | ||
| + | * After 22nd June assume 50+ hours working, to make up for lost time during University term | ||
| + | 25th June – 2nd July | ||
| + | * Milestone 2: Fluid system complete and fully bug tested. | ||
| + | * Start work on the collision system | ||
| + | 2nd July – 9th July | ||
| + | * Preparing for mid-term evaluations, fixing all current code up to this point which will be around two thirds of the whole project | ||
| + | * Continue work on the collision system | ||
| + | 9th July - 16th July | ||
| + | * Continue work on the collision system | ||
| + | 16th July – 23rd July | ||
| + | * Milestone 3: Collision system completed | ||
| + | * From this point forward, start black box testing to ensure everything works | ||
| + | 23rd July – 30th July | ||
| + | * Milestone 4: Black box testing complete | ||
| + | * Start white box testing to ensure code is of a high standard | ||
| + | 30th July – 3rd August | ||
| + | * Milestone 5: White box testing complete | ||
| + | * All following time is a buffer zone. If everything complete, begin work on adding more functionality to the fluid system, namely the underwater physics | ||
| + | 3rd August – 17th August | ||
| + | * I will be in Germany during this period on holiday. I will however, still have a laptop as well as internet access so although this is a critical time with respect to final evaluations and so on, there is no reason for me to not be able to work | ||
| + | * Time spent cleaning up code if needed, write documentation to enable users to easily utilise any of the functionality of the simulation system. | ||
| + | 17th August – 24th August | ||
| + | * Any last minute fixes are made, final evaluations sorted and project finished. | ||
| + | * Milestone 6: Project finish, submit evaluations. | ||
Revision as of 09:29, 8 May 2012
Contents
Google Summer of Code 2012
Current
Status: Working on compiling BRL-CAD with Bullet Library
TODO: Gain Commit access before 21st May
Log
April 2012
BRLCAD compiled and run with Windows Visual Studio x64 Debug
May 2012
8th : Updated Wiki pages
Development Schedule
(Unless otherwise specified, 40+ hours of work to be assumed):
23rd April – 5th May
- Flesh out any last details in project, have all objectives clear and the schedule complete.
- Gain commit access before or during this point
5th May – 21st May
- Learn as much about any relevant libraries such as Bullet, and BRL-CAD libraries such as librt and libged as I can, to enable me to be able to get straight into coding with the knowledge of what is already there and how to use it.
- Start writing function outlines, header files to make it clearer as to what goes where and how to reuse code efficiently.
- Iron out any current bugs in the simulation files, to ensure a fully working simulation environment.
21st May – 28th May
- Coding begins. Start by working on the gravitational system as this will be the easiest to implement and so will take the shortest amount of time, and will make sure I am completely familiar with the code.
28th May – 4th June
- Milestone 1: Gravitational system complete and fully bug tested.
- Once milestone 1 is reached, begin work on the fluid system, starting with functions to calculate drag on surfaces
4th June – 11th June
- Exam period starts at University, limited time available.
- In available time, work on drag functions and start to implement functions to resolve the forces from the drag (In x,y and z directions)
11th June – 18th June
- Exam period ends
- Carry on implementing functions to resolve forces and start on functions to resolve moment forces to show rotation in the simulation
18th June – 25th June
- Continue working on the fluid system and begin bug testing
- After 22nd June assume 50+ hours working, to make up for lost time during University term
25th June – 2nd July
- Milestone 2: Fluid system complete and fully bug tested.
- Start work on the collision system
2nd July – 9th July
- Preparing for mid-term evaluations, fixing all current code up to this point which will be around two thirds of the whole project
- Continue work on the collision system
9th July - 16th July
- Continue work on the collision system
16th July – 23rd July
- Milestone 3: Collision system completed
- From this point forward, start black box testing to ensure everything works
23rd July – 30th July
- Milestone 4: Black box testing complete
- Start white box testing to ensure code is of a high standard
30th July – 3rd August
- Milestone 5: White box testing complete
- All following time is a buffer zone. If everything complete, begin work on adding more functionality to the fluid system, namely the underwater physics
3rd August – 17th August
- I will be in Germany during this period on holiday. I will however, still have a laptop as well as internet access so although this is a critical time with respect to final evaluations and so on, there is no reason for me to not be able to work
- Time spent cleaning up code if needed, write documentation to enable users to easily utilise any of the functionality of the simulation system.
17th August – 24th August
- Any last minute fixes are made, final evaluations sorted and project finished.
- Milestone 6: Project finish, submit evaluations.
