Skip to content

Final Technical Report Review #31

@petrusomc

Description

@petrusomc
  • a keywords section
  • Sentence: This is not because the original simulator was poorly made, it was very well made given when it was written. Its problems stem mostly form simply being out dated.
    • use a semicolon instead of a comma. I am no grammar expert, but I think the This is not because the original simulator was poorly made and it was very well made given when it was written are two complete thoughts and can be separated.
  • elaborate on the design. How did you chose the tools you used. Maybe why you chose the tools/languages you used. You can go into specific obstacles you came across and executive design choices you made because of the obstacles.
  • in your design, you can also talk about why you chose to implement a model, view, controller design pattern and why that fit in with your project
  • can add a few of kepler's equations you used
  • can also add code snippets for examples that used kepler's laws and explain these equations in your development section
  • I really enjoyed the report and your project topic. I assume that you validated that your predictions and model is correct through kepler's laws (calculating by hand)? If not, you can explain that somewhere in there too!
  • references in some sort of IEEE format

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions