You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i noticed "duplicate" copies of robot.py in two directories
one is within the /usr/local/lib....eggfile/jetbot path
the other is within the obvious workspace/jetbot/jetbot path
making changes to the robot.py in the workspace directory didnt affect the code becuase the installed version is in the one in the usr directory as determined by inspection
however making changes to the robot.py file in usr directory gets overwritten with the original code every time i run build.sh in the docker folder.
any suggestions to make the changes permanent?
or any suggestions to make changes to robot.py
there seems to be people who have successfuly done this but they didnt document it properly for others to follow.
thanks
The text was updated successfully, but these errors were encountered:
solved!
shouldnt have run build.sh
but to those wanting make changes to robot.py or other source files make sure to inspect where the installed source file is first and modify that version.
also had to access the file via jupyter terminal.
it is invisible from regular/linux terminal
i noticed "duplicate" copies of robot.py in two directories
one is within the /usr/local/lib....eggfile/jetbot path
the other is within the obvious workspace/jetbot/jetbot path
making changes to the robot.py in the workspace directory didnt affect the code becuase the installed version is in the one in the usr directory as determined by inspection
however making changes to the robot.py file in usr directory gets overwritten with the original code every time i run build.sh in the docker folder.
any suggestions to make the changes permanent?
or any suggestions to make changes to robot.py
there seems to be people who have successfuly done this but they didnt document it properly for others to follow.
thanks
The text was updated successfully, but these errors were encountered: