hey @jeffzma2000 , i figured this would be a good introduction to using github in a project.
It is possible to reference code in issues and discuss in cleanly
you can go to your code in your browser (here)[] and press "y", this will git a persistent link. Then on the left hand side you can reference specific lines (shift click). Notice that the url has changed.
You can then copy/paste that url into issues and github will render the code cited.
So in the future when you want someone else to look at your code just paste that link as I did below:
hey @jeffzma2000 , i figured this would be a good introduction to using github in a project.
It is possible to reference code in issues and discuss in cleanly you can go to your code in your browser (here)[] and press "y", this will git a persistent link. Then on the left hand side you can reference specific lines (shift click). Notice that the url has changed. You can then copy/paste that url into issues and github will render the code cited.
So in the future when you want someone else to look at your code just paste that link as I did below:
https://github.com/CNCLgithub/galileo-ramp/blob/e003957c5ad1fb69b2c0c15e8bda0c5a5d6843f7/scripts/stimuli/create_3ball_scene.py#L59-L75
Now to the code.
ihere just describes a unique index for each scene. https://github.com/CNCLgithub/galileo-ramp/blob/e003957c5ad1fb69b2c0c15e8bda0c5a5d6843f7/scripts/stimuli/create_3ball_scene.py#L71I would just keep a counter at the beginning of the first for loop and increment it accordingly.
also remove line 75, the
passstatement was only there as a placeholder https://github.com/CNCLgithub/galileo-ramp/blob/e003957c5ad1fb69b2c0c15e8bda0c5a5d6843f7/scripts/stimuli/create_3ball_scene.py#L75