Here is the code FSP:

const MAX_DIST = 5
range DIST = 0..MAX_DIST
const MAX_SEC = 12
range SEC = 0..MAX_SEC
const MAX_VEL = 5
range VEL = 1..MAX_VEL

ENGINE = (engineOn ->THROTTLE),

THROTTLE = ( start -> SPEED_COUNTER[1]
| engineOff ->ENGINE

),

SPEED_COUNTER[v:VEL] = ( when(v<MAX_VEL) accelerator[v] ->SPEED_COUNTER[v+1]
| when(v>1) reduceSpeed[v-1] ->SPEED_COUNTER[v-1]
| engineOff ->ENGINE
| when(v>1) signal_received ->metri250->DISTANCE[MAX_DIST][v]
| csr ->beep->CSR[v][MAX_SEC]
),

CSR[v:VEL][s:SEC] =
(when(s>0)tick->CSR[v][s-1]
|when(s==0) brake->SPEED_COUNTER[1]
|when(s>0)release -> CHECK_DISTANCE[MAX_DIST][v]
|signal_received -> release -> SPEED_COUNTER[v]
),

DISTANCE[d:DIST][v:VEL] =
(when(d>0)avanza50mt->DISTANCE[d-1][v]
|when(d==0) brake->SPEED_COUNTER[1]
|when(d>0)csr ->beep->CSR[v][MAX_SEC]
),

CHECK_DISTANCE[c:DIST][v:VEL] =
(when(c>0)avanza50mt->CHECK_DISTANCE[c-1][v]
|when(c==0) brake->SPEED_COUNTER[1]
|when(c>0) signal_received ->SPEED_COUNTER[v]
).

Thanks for any reply if you need more information contact me.

Sincerely Stefano

Thats the order of the functions I call:
ltsaEditor.doParse(true);
ltsaEditor.doCompileCompose(complFSP);
ltsaEditor.doLiveness(firstAssertionName);

My assumption is as follows:
I think you do the parsing/compiling in a seperate thread / job ? Maybe the parsing/compiling is not yet finished when I already call doLiveness sothat doLiveness cannot work
But thats of course just an assumption as I cannot see into your code.

Many greetings

Ive got a question about the functionality of the doLiveness method. If I call this function in my program right after intialising the fsp editor and compiling the fsp text nothing happens.
If I do the same manually, that means, open Editor, compile the fsp text und check one assertion, it works fine.
What is the difference between calling this function in the gui and in the program
I tracked the execution of these both approaches in the debugger and the only difference I ve noticed is as follows:
In the case I call it in the GUI: the variable property with the name of the assertion keeps its value all the time
In the case I call it in my program: the variable property loses its value after 2 or 3 steps and becomes ""

Whats the reason for this?

Thanks

Many greetings

My problem is not project specific. Sorry my English is no very good, but nevertheless I try it_:)

If I use your standalone ltsa tool I go to Check->LTL and choose one assertion. Everything works fine
If I take the same FSP text and use it in the LTSA eclipse plugin I cannot find this function. In the outline view no assertions is shown and there is no "check->ltl" option.

Many greetings

Anyway, back on 32bit Eclipse 3.5 MAC OS X and I had more time to "grab a mac" to rebuild the projects… seems like an Execution Environment issue (so much for Technology Independence!).

I put this test build on a new update site here: MAC OSX WSE Install which appears to install ok.

Not everything is working correctly (SWT issues seem to be evident), but should let you play a bit further.

But i have another problem. While developing my plugin I 've noticed that i cannot more check assertions. I dont find any options in the gui although i defined two assertions in the lts file? Have you removed this function?
doLiveness(nameOfAssertion) has no effect.

Many Greetings

http://www.doc.ic.ac.uk/ltsa/eclipse/install35

otherwise download the libs from http://www.doc.ic.ac.uk/ltsa/eclipse/install35/plugins/

Can you help me?

If it all proves successful, you might like to share your design on this wiki! :-)

You can use the following (inherited from ltsaeclipseEditor) to parse, compile, check properties and assertions…

 doParse(boolean updatePages) - where updatePages refreshes the LTS Output and Draw views doCompile(String compositionString) - where compositionString is the name of the composition to compile doAnalyse() - after doCompile, performs default safety check on properties specified in the model compiled doLiveness(string property) - where property is the name of the assertion to check 

LTSAAdmin

I already read this article. But my problem is not the extending or changing your plugin. I don't get how i can address your functions within my plugins (for example compile, or check assertions etc)

many greetings

There is an example of extending the plug-in (with your own editor - which could just be an extended LTS editor) here:

Installing the Sample New Editor plug-in

Try this first and let me know if it meets your requirements.

LTSAAdmin

Again i want to say that I appreciate your eclipse ltsa plugin. But is it possible that you introduce extension points oder an api? I would like have the function that i give over a valid ltsa file / text and receive the result of the anaylzis, especially the information whether my assertions/fluents hold.

Many Greeting

I have not had time to test it properly, so please let me know if you encounter problems.

The new version is in incubation here:

http://www.doc.ic.ac.uk/ltsa/eclipse/installtest/site.xml

Not sure if you received my last email yesterday, please let me know if there is anything I am seriously overlooking - this is the only feature that is preventing me from running the plugin in Eclipse.

I am referring to the Transitions tab from the LTS Draw perspective. I can draw it fine, I can see the alphabet fine and when I click on Transitions nothing comes up (I take it to have the equivalent functionality of selecting Window-> Transitions in the full LTSA tool. I am running it on XP with the latest Java version and Eclipse 3.4.2 if it is of any help.

Regards,
George