Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
183_notes:vpython_resources [2015/05/28 12:04] – [Software for Projects] caballero | 183_notes:vpython_resources [2020/07/16 04:51] – [PhysUtil] pwirving | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
+ | |||
+ | In class, you will make use of [[https:// | ||
- | In class, you will make use of [[http:// | ||
===== VPython ===== | ===== VPython ===== | ||
- | VPython | + | The class uses Glowscript and by default |
* create visual objects in 3 dimensions, | * create visual objects in 3 dimensions, | ||
Line 10: | Line 11: | ||
* move the visualization around with mouse interactions | * move the visualization around with mouse interactions | ||
- | Extensive documentation for VPython is [[http:// | + | All of this allows us to create computational models that are modeling real-world physical phenomenon that can help you gain an understanding and insight into physics concepts that you will interact within this class. |
===== PhysUtil ===== | ===== PhysUtil ===== | ||
- | PhysUtil is a module for VPython that makes it simpler to create highly visual simulations. With very little code, PhysUtil lets you: | + | The majority of the codes that you will use in this class will start with two lines. The first line tells the program which version of Glowscript it is using: " |
+ | |||
+ | The second line which will not always be there but will be the majority of the time will be " | ||
* generate motion maps, {{: | * generate motion maps, {{: | ||
Line 20: | Line 24: | ||
* import CSV data | * import CSV data | ||
- | Extensive | + | For folks who are interested in learning more about PhysUtil and what it does, there is extensive |
+ | |||
+ | Message from Paul: //{You will have heard me say this already but I want to reaffirm that you are not expected to learn a whole language when taking this class. The focus is on gaining an understanding of how to read code and make small edits. Before designing this class I had no real coding experience and so I want to highlight something that might lead to frustration as it did for me when I started learning some basic coding. Errors can drive you nuts. BUT, learning the skill of debugging an error is important and will hold to you in any future coding experiences. It is transferrable to other classes and future career aspirations and is a legitimate problem-solving approach that is not just applicable to code. So, by all means, get frustrated but remember that encountering errors in your code is not a failure on your part but just an opportunity to develop a new skill and also remember to celebrate the victories when you get your code to do what you intend it to do.} // | ||
+ | |||
+ | ===== Python Troubleshooting ===== | ||
+ | * Syntax errors – A syntax error occurs when python is unable to interpret a line of code. This usually occurs because of a simple typo, misspelling, | ||
+ | * Indentation errors – This is caused by an inconsistency in the indentation of the while loop. To fix this highlight the while loop, click “Format” (on the top bar of the laptop), click “dedent region”, then use tab to re indent everything that was indented to start. | ||
+ | * Float Error: scalar vs. vector – when coding using both scalar and vector values, keep in mind that you cannot multiply, divided, or put a vector to the power of a number without first taking the magnitude of the vector (to make the vector a scalar value). | ||
+ | * Name Error – This error occurs when you are trying to call a variable that has not already been defined above. To fix this, the line that defines the variable must be moved above the equation that the variable is being used in. This also occurs if the defined variable is misspelled. | ||
+ | * Type Error – This error is much like a float error. | ||
+ | * Spazzing Graph – When putting in the first line of code it needs to be placed under the # | ||
+ | * Magnitude vs. Dot product – to find the size or absolute value of a vector, take the magnitude of that vector; this yields a scalar quantity with no directional information and is never negative. | ||
+ | |||
+ |