@shadow pilot
Python help channel opened
#🔒 Help breaking this while loop
chilly ruinBOT
Python help channel opened
shadow pilot
why wont it let me upload my code : (
chilly ruinBOT
chilly ruinBOT
sterile estuary
Either paste it into chat and use the above to format it, or use the paste service if it is too long for that
olive terrace
Yes
shadow pilot
okay nice
so basically, now that you guys can see my code, this is a lego mindstorms project for school with python. I want to log various parts of the robots movement actively as it moves around, this is just a simple test code. I have the issue where it keeps logging forever and doesnt move onto the next line
i want to know how i would break the while loop
sterile estuary
Can I assume its the while loop in motion that is the issue?
olive terrace
When do you want to break it?
def motion(left_motor, right_motor, gyro, straight_distance, x):
while x == 1:
data.log(watch.time(), left_motor.angle(), right_motor.angle(), gyro.angle(), straight_distance)
correct
olive terrace
This is the problem?
shadow pilot
yes
olive terrace
In this case I don't think you want the while loop in the function.
You'd probably have the while loop in your main body of code.
sterile estuary
It never gets to line 65, because line 64 takes forever as it gets stuck in a loop without a break and where x doesn't change.
shadow pilot
right
olive terrace
It never gets to line 65, because line 64 takes forever as it gets stuck in a lo...
Yeah, so I would probably just remove the while loop from the function.
shadow pilot
You'd probably have the while loop in your main body of code.
how else would i log continously
🤔
olive terrace
how else would i log continously
You could probably just move your while loop to your main body of code, outside of where the function is.
I don't really know much about ev3 though.
sterile estuary
motion(...)
wait(5)
motion(...)
wait(5)```
Which you could put into a loop, like a `for` loop that goes 500 timesev3.speaker.beep() # Signal that the gyro is resetting, do not touch after the beep
gyro.reset_angle(0) # Reset gyro
x=1
straight_distance = 0
straight_distance = distance(left_motor, right_motor, straight_distance)
drive.base(5)
while x == 1:
data.log(watch.time(), left_motor.angle(), right_motor.angle(), gyro.angle(), straight_distance)
wait(2000)
x=0
drive.base_stop
ev3.speaker.beep() # Signal that program is done
like this?
shadow pilot
```py
motion(...)
wait(5)
motion(...)
wait(5)```
Which you could put into a loop...
what do you mean by this
olive terrace
what do you mean by this
You basically put your log function in a loop
Instead of having a loop in the function itself.
olive terrace
Sometimes the simplest ideas are best
shadow pilot
i am going to branch it out so i wanted an easier way to just stop the loop
because that would mean i would have to time how long every motion takes
the goal is to have this act as a part of an odometry system
sterile estuary
i am going to branch it out so i wanted an easier way to just stop the loop
You're going to have to explain more about what other conditions would cause you to want to break the loop. Which variables having which values mean you want to stop? Other than reaching 2000 of wait time?
I was suggesting something like:
for _ in range(200):
data.log(watch.time(), left_motor.angle(), right_motor.angle(), gyro.angle(), straight_distance)
wait(10)
okay so essentially, i want to have it so that while the robot is moving, it will log data, and then when it stops moving, it will stop logging data, and if it moves after that it will begin logging again
basically i want it to constantly check for movement
x is just a placeholder at the momenet
i will probably use a "if the motor speed is above 0, log data" type loop
but i think i will run into the same issue
sterile estuary
okay so essentially, i want to have it so that while the robot is moving, it wil...
Hmm, sounds like you don't necessarily want it to stop logging, you just should have a if condition in your logging function that doesn't do the logging if it hasn't moved since the last report.
shadow pilot
right that makes sense
i am just curious as to how i would make it constantly check
because i assume if i would enable that function when the robot boots, it will see that there isnt movement and continue on
and not log anything even if the robot moves afterwards
sterile estuary
So in general, you can do, say drive.base(15) but during the execution of that ALSO do something else. Python generally only does one thing at a time unless you're doing threading or multiprocessing and most libraries aren't going to behave nicely for that. So if you want it to be constantly checking if it has moved, then you need to be constantly running an if statement that checks if it has moved. One way to do this would be to create your own move functions that move 1, log, move 1, log, and loop that until it hits its target amount of movement. Now you can just call your own custom move function when you want it to move
And if it is only moving when you've told it to move, then there isn't really a need to check if its moving or not, right? You can just have it log its movements occassionally throughout your custom movement function and don't log anything otherwise.
shadow pilot
true
i might get rid of continous logging
realistically i only need it once the movement is done
chilly ruinBOT
Python help channel closed