generated from mwc/lab_scatter
I was all worried about how I was going to scale the axes and make the tick marks and then it was already part of the template! That said, it was super helpful to be able to see under the hood on how all the formatting and setup was done. Overall the process went well. Having the structure for part of drawing the axes made that section very smooth. I had made a typo in the dtaw_points portion where I had used () instead of [] when indexing a list amd the error message was just cryptic enough to make me think I had made some other, more serious mistake after correcting the typo; turns out, I had just not resaved scatterplot.py after correcting so of course I was going to keep getting the same error message. Other than that, the assignment was straightforward and implementing the functions we made in transform.py was easy enough to get the axes drawn and points plotted. I'm happy with how it turned out. Top-down design made this process accessible, as far as I'm concerned. Without breaking this up into small steps, there's no way I would have been able to do this all at once. I really appreciated your clarity and breakdown throughout the prompt. The whole system up to this point has been a great model for how I need to approach projects/labs in the future with my courses. When I was teaching physics, it was sort of second-nature to go through an example, break down a problem, and then have the students apply it themselves but one thing I haven't dialed in on the cs-side yet is how much do I give to the students and at what point can they do it themselves. I usually fall into the trap of wanting them to do too much too fast and when they're confronted with a problem they (think they) can't solve, they shut down. |
||
---|---|---|
.commit_template | ||
.gitignore | ||
constants.py | ||
generate_data.py | ||
planning_scatter.md | ||
plotting.py | ||
poetry.lock | ||
pyproject.toml | ||
scatterplot.py | ||
test_transform.py | ||
ticks.py | ||
transform.py |