With ros 7.6 I tried to write a script directly in Scheduler and this works.
I ask is it correct to do this or what problems might it bring?
Re: Writing a script in Scheduler.
There's no point in making scripts separately and then running them in the scheduler.
Non ha senso fare gli script a parte e poi richiamarli nello scheduler...
Non ha senso fare gli script a parte e poi richiamarli nello scheduler...
Re: Writing a script in Scheduler.
So you say that if you make a script that needs to be scheduled, just copy/past script in the scheduler and do not use the script function at all?
Re: Writing a script in Scheduler.
Indeed...
You don't have a drop-down menu where you can choose the script, but an area identical to that of the scripts where you can insert... the script...
In the scheduler if you "call" the script, you just create a script that calls the script...
If you need to call the source of a script to do something else, you can do exactly the same with the scheduler text.
Difference between scheduler and script: none except that the script doesn't start by itself, the scheduler can put a "timer" on it...
You don't have a drop-down menu where you can choose the script, but an area identical to that of the scripts where you can insert... the script...
In the scheduler if you "call" the script, you just create a script that calls the script...
If you need to call the source of a script to do something else, you can do exactly the same with the scheduler text.
Difference between scheduler and script: none except that the script doesn't start by itself, the scheduler can put a "timer" on it...
Re: Writing a script in Scheduler.
Learning new things every day. Thanks
Re: Writing a script in Scheduler.
Yeslargelya difference without distinction.With ros 7.6 I tried to write a script directly in Scheduler and this works.
I ask is it correct to do this or what problems might it bring?
Only two minor differences:
- 如果你需要一样的script in *multiple* scheduled tasks.... In this case, it be better to have your script in /system/scripts, so there be only one copy of your code to edit or change.
- Or you want "manually" run your script... e.g. /system/script has "run script" while schedule does not (without changing the schedule).
- In Schedule, you can just put the name of the script as the "On Event" to invoke another script, while in /system/script you have to use the full command to call another script.
Re: Writing a script in Scheduler.
thanks for the info, and since you can't put reactions to every post I'll put them here
Re: Writing a script in Scheduler.
Better to have each script copied multiple times for each scheduler.[*] If you need the same script in *multiple* scheduled tasks.... In this case, it be better to have your script in /system/scripts, so there be only one copy of your code to edit or change.
If for some reason you modify the script that is called by multiple schedules
and for some reason later turns out to be faulty, not just one, but all of the schedules stop working.
Or modifying the script could cause one or more schedules to no longer behave correctly if the script is modified,
for some unforeseeable reason at the outset.
[*] Or you want "manually" run your script... e.g. /system/script has "run script" while schedule does not (without changing the schedule).
not true:
Code:Select all
[[:parse [/system scheduler get on-event]]] Re: Writing a script in Scheduler.
To the OP, as you can see it doesn't matter. This is really just personal preferences.
FWIW something I do neither. Instead of script or schedule, I sometimes just copy a script with functions to the file system, and then use :import it (from CLI, schedule, etc.) to load the all my script functions. This is pretty quick to load a very large script file, and has a verbose=yes and start-after= options so you can debug a large script or ROS functions. So the file system be the third way, all have some differences (as you see here)
I have no idea why there is a strong opinion that ONLY valid way is ALWAYS put code in the schedule itself & never use schedule to call scripts – everything has it's place.
Yes I know how parse works. I was referring to winbox dialog box for "System Scripts" that has a nice little "Run Script"BUTTON... but schedule does not. At the CLI, youcouldcall :parse with [[[]]] and remember it's actually "on-event" not "script"... But "saved code" in /system/scripts, can be called using "run" (e.g. /system/script/run
FWIW something I do neither. Instead of script or schedule, I sometimes just copy a script with functions to the file system, and then use :import it (from CLI, schedule, etc.) to load the all my script functions. This is pretty quick to load a very large script file, and has a verbose=yes and start-after= options so you can debug a large script or ROS functions. So the file system be the third way, all have some differences (as you see here)
I have no idea why there is a strong opinion that ONLY valid way is ALWAYS put code in the schedule itself & never use schedule to call scripts – everything has it's place.
not true:[*] Or you want "manually" run your script... e.g. /system/script has "run script" while schedule does not (without changing the schedule).
Code:Select all
[[:parse [/system scheduler get on-event]]] Yes I know how parse works. I was referring to winbox dialog box for "System Scripts" that has a nice little "Run Script"BUTTON... but schedule does not. At the CLI, youcouldcall :parse with [[[]]] and remember it's actually "on-event" not "script"... But "saved code" in /system/scripts, can be called using "run" (e.g. /system/script/run