Run Script -> Ops Example -> No Prompt? about opensatkit

[dmccomas]

I changed the 'Stop cFS" so it usses an executive service command thinking it's more graceful but I may go back to the old way that stops all core-cpu1 processes.

…

On Tue, May 12, 2020 at 6:39 PM Dan Fellin ***@***.***> wrote: Yup, running everything locally! Ok now everything is working great. It looks like the cause was that sometimes I have some "extra" ./core-cpu1 processes that hang around after playing around with OpenSatKit for awhile, even after trying to hit Stop CFS. [image: image] <https://user-images.githubusercontent.com/847862/81752427-47c6b000-9466-11ea-8dbd-c2ea436605c8.png> If I make sure those are all dead and then do a fresh ruby Launcher for cosmos, then the ops script works great! Thanks! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#30 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMGKCGVHFUDIHU2DSCVWWLRRHFZHANCNFSM4L4NT25Q> .

[dmccomas]

If the cFS is not running when you start the simsat ops example a message box should be displayed stating the cFS will be started and a new terminal window should appear. It's the same script that is used to start the cFS that is used by the main window.

Are you running everything locally?

[eupharis]

Yup, running everything locally!

Ok now everything is working great.

It looks like the cause was that sometimes I have some "extra" ./core-cpu1 processes that hang around after playing around with OpenSatKit for awhile, even after trying to hit Stop CFS.

If I make sure those are all dead and then do a fresh ruby Launcher for cosmos, then the ops script works great! Thanks!