Failed to SIMULATE #80
-
I have added PATH environment variables as showed in the fisrt figure. But when I tried to execute the "SIMULATE" I failed, as showed in the second figure. How can I handle this question? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hi @lht011129 , Thank you for trying out FRET! The SIMULATE button is disabled because FRET checks whether NuSMV is installed, by checking the output of a call to a
Please don't forget to let us know if the above resolves your issue. Best Regards, Andreas |
Beta Was this translation helpful? Give feedback.
-
Hi Andreas,
Thank you for your mail! With the ways provided by you, I have resolved my issue. Thank you again!
Best Regards,
Lin
…------------------ 原始邮件 ------------------
发件人: "NASA-SW-VnV/fret" ***@***.***>;
发送时间: 2024年5月13日(星期一) 晚上10:38
***@***.***>;
***@***.******@***.***>;
主题: Re: [NASA-SW-VnV/fret] Failed to SIMULATE (Discussion #80)
Hi @lht011129 ,
Thank you for trying out FRET! The SIMULATE button is disabled because FRET checks whether NuSMV is installed, by checking the output of a call to a nusmv command. Our next release, which is coming up pretty soon, addresses this in a more robust way. In the meantime, you have two ways to resolve this locally:
Rename the NuSMV binary to nusmv, that is:
mv /home/szy/Desktop/NuSMV-2.6.0-Linux/bin/NuSMV /home/szy/Desktop/NuSMV-2.6.0-Linux/bin/nusmv
Create a symbolic link called nusmv , pointing to the NuSMV binary. You can do so by heading into the NuSMV folder (/home/szy/Desktop/NuSMV-2.6.0-Linux/bin , according to your screenshot) and run:
ln -s /home/szy/Desktop/NuSMV-2.6.0-Linux/bin/NuSMV /home/szy/Desktop/NuSMV-2.6.0-Linux/bin/nusmv
Please don't forget to let us know if the above resolves your issue.
Best Regards,
Andreas
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Hi @lht011129 ,
Thank you for trying out FRET! The SIMULATE button is disabled because FRET checks whether NuSMV is installed, by checking the output of a call to a
nusmv
command. Our next release, which is coming up pretty soon, addresses this in a more robust way. In the meantime, you have two ways to resolve this locally:NuSMV
binary tonusmv
, that is:nusmv
, pointing to theNuSMV
binary. You can do so by runningPlease don't forget to let us know …