Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| ece4560:piktul:05resratepos [2017/10/22 16:30] – [The Member Functions] pvela | ece4560:piktul:05resratepos [2024/08/20 21:38] (current) – external edit 127.0.0.1 |
|---|
| end | end |
| </code> | </code> |
| This can be a hidden function within the ''genPositionTrajectory'' member function or it can be a protected member function (the easiest would be to make it a public member function). It is the main part that has the resolved rate equations. Code stubs to insert into the piktul class can be found here: {{ece4560:piktul:resolvedStubs.m|stubs}}. | This can be a hidden function within the ''genPositionTrajectory'' member function or it can be a protected member function (the easiest would be to make it a public member function). It is the main part that has the resolved rate equations. Code stubs to insert into the piktul class can be found here: {{ece4560:piktul:resolvedStubs.m|stubs}}. The code stubs have ''posODE'' as a hidden function within a function. The documentation of the code stub provides additional clues as to how to code the entire learning module up. |
| | |
| | Overall, try to have functionality or code that seems inherent to the piktul actually reside in the ''piktul'' class. Some can be outside of it. I leave this as a judgement call, but definitely you should be considering what functionality should actually be implemented within the class and how it supports abstraction/encapsulation as per good coding design. |
| | |
| | |
| |
| ==== Playing Back as a Movie ==== | ==== Playing Back as a Movie ==== |
