Hi Gabi,
Ahh, now I understand. Any entity answers to mooseModel, so you can do:
FAMIXClass>>someMethod self mooseModel ...
Great that you are using the Pharo version. Just for convenience, you can find the latest development image here: http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/a...
Please let us know if you have further problems.
Cheers, Doru
On 12 Apr 2010, at 18:18, Gabriela Arevalo wrote:
Hi Doru,
Thanxs for answering so quick.
I am attaching an jpg to illustrate my problem :)
If I evaluate MooseModel root, I get an instance of MooseModel that contains all the existing models. In the image you see that there are two models: Collections and SequenceableCollection, and SequeanceableCollection is selected to be the current one of the analysis.
How can I access to that model if I am coding any property in a class? I checked the entities to know if each entity knows the model which belongs to, but it seems not.
In the long past we could do ModelManager uniqueInstance currentModel, but now, how do I know that information?
I am using Pharo version. I used the VW version during the weekend, but it seems that there are some code broken and I could not manage to make it work.
Cheers,
Gabi
2010/4/12 Tudor Girba tudor.girba@gmail.com Hi Gabi,
Nice to hear from you :).
ModelManager was replaced by just another Model that holds Models. To get to it, you do "MooseModel root" and if you want to see allModels from there, you do "MooseModel root allModels".
Yes, properties are defined using pragmas.
Which Moose are you using? Pharo or VW?
Cheers, Doru
On 12 Apr 2010, at 02:11, Gabriela Arevalo wrote:
Hi guys,
I have two basic questions regarding the implementation of Moose
- How do we manage now the currentModel (the selected Model in the
Moose UI)? A long time ago :) :), we have had the ModelManager class and we could do ModelManager uniqueInstance currentModel
- Properties: I have seen that we are using pragmas from the
instance side. Is it right? Or are there any other way of specifying them?
Cheers,
Gabi _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Beauty is where we see it."
-- www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
Hi Gabi
Just from experience, if you send mooseModel to all entities in a large model, it can take a long time. So if you run into scalability problem, it may come from that. Now depending on your use case, there might be other solutions.
On 12 avr. 2010, at 19:57, Tudor Girba wrote:
Hi Gabi,
Ahh, now I understand. Any entity answers to mooseModel, so you can do:
FAMIXClass>>someMethod self mooseModel ...
Great that you are using the Pharo version. Just for convenience, you can find the latest development image here: http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/a...
Please let us know if you have further problems.
Cheers, Doru
On 12 Apr 2010, at 18:18, Gabriela Arevalo wrote:
Hi Doru,
Thanxs for answering so quick.
I am attaching an jpg to illustrate my problem :)
If I evaluate MooseModel root, I get an instance of MooseModel that contains all the existing models. In the image you see that there are two models: Collections and SequenceableCollection, and SequeanceableCollection is selected to be the current one of the analysis.
How can I access to that model if I am coding any property in a class? I checked the entities to know if each entity knows the model which belongs to, but it seems not.
In the long past we could do ModelManager uniqueInstance currentModel, but now, how do I know that information?
I am using Pharo version. I used the VW version during the weekend, but it seems that there are some code broken and I could not manage to make it work.
Cheers,
Gabi
2010/4/12 Tudor Girba tudor.girba@gmail.com Hi Gabi,
Nice to hear from you :).
ModelManager was replaced by just another Model that holds Models. To get to it, you do "MooseModel root" and if you want to see allModels from there, you do "MooseModel root allModels".
Yes, properties are defined using pragmas.
Which Moose are you using? Pharo or VW?
Cheers, Doru
On 12 Apr 2010, at 02:11, Gabriela Arevalo wrote:
Hi guys,
I have two basic questions regarding the implementation of Moose
- How do we manage now the currentModel (the selected Model in the Moose UI)?
A long time ago :) :), we have had the ModelManager class and we could do ModelManager uniqueInstance currentModel
- Properties: I have seen that we are using pragmas from the instance side. Is it right? Or are there any other way of specifying them?
Cheers,
Gabi _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Beauty is where we see it."
-- www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Thanks Simon,
this info is important.
Cheers, Alexandre
On 12 Apr 2010, at 15:27, Simon Denier wrote:
Hi Gabi
Just from experience, if you send mooseModel to all entities in a large model, it can take a long time. So if you run into scalability problem, it may come from that. Now depending on your use case, there might be other solutions.
On 12 avr. 2010, at 19:57, Tudor Girba wrote:
Hi Gabi,
Ahh, now I understand. Any entity answers to mooseModel, so you can do:
FAMIXClass>>someMethod self mooseModel ...
Great that you are using the Pharo version. Just for convenience, you can find the latest development image here: http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/a...
Please let us know if you have further problems.
Cheers, Doru
On 12 Apr 2010, at 18:18, Gabriela Arevalo wrote:
Hi Doru,
Thanxs for answering so quick.
I am attaching an jpg to illustrate my problem :)
If I evaluate MooseModel root, I get an instance of MooseModel that contains all the existing models. In the image you see that there are two models: Collections and SequenceableCollection, and SequeanceableCollection is selected to be the current one of the analysis.
How can I access to that model if I am coding any property in a class? I checked the entities to know if each entity knows the model which belongs to, but it seems not.
In the long past we could do ModelManager uniqueInstance currentModel, but now, how do I know that information?
I am using Pharo version. I used the VW version during the weekend, but it seems that there are some code broken and I could not manage to make it work.
Cheers,
Gabi
2010/4/12 Tudor Girba tudor.girba@gmail.com Hi Gabi,
Nice to hear from you :).
ModelManager was replaced by just another Model that holds Models. To get to it, you do "MooseModel root" and if you want to see allModels from there, you do "MooseModel root allModels".
Yes, properties are defined using pragmas.
Which Moose are you using? Pharo or VW?
Cheers, Doru
On 12 Apr 2010, at 02:11, Gabriela Arevalo wrote:
Hi guys,
I have two basic questions regarding the implementation of Moose
- How do we manage now the currentModel (the selected Model in
the Moose UI)? A long time ago :) :), we have had the ModelManager class and we could do ModelManager uniqueInstance currentModel
- Properties: I have seen that we are using pragmas from the
instance side. Is it right? Or are there any other way of specifying them?
Cheers,
Gabi _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Beauty is where we see it."
-- www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
This should not be the case. Every subclass of MooseEntity stores the mooseModel in the attribute dictionary from EntityState. Where did you notice the slowdown?
Cheers, Doru
On 12 Apr 2010, at 21:38, Alexandre Bergel wrote:
Thanks Simon,
this info is important.
Cheers, Alexandre
On 12 Apr 2010, at 15:27, Simon Denier wrote:
Hi Gabi
Just from experience, if you send mooseModel to all entities in a large model, it can take a long time. So if you run into scalability problem, it may come from that. Now depending on your use case, there might be other solutions.
On 12 avr. 2010, at 19:57, Tudor Girba wrote:
Hi Gabi,
Ahh, now I understand. Any entity answers to mooseModel, so you can do:
FAMIXClass>>someMethod self mooseModel ...
Great that you are using the Pharo version. Just for convenience, you can find the latest development image here: http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/a...
Please let us know if you have further problems.
Cheers, Doru
On 12 Apr 2010, at 18:18, Gabriela Arevalo wrote:
Hi Doru,
Thanxs for answering so quick.
I am attaching an jpg to illustrate my problem :)
If I evaluate MooseModel root, I get an instance of MooseModel that contains all the existing models. In the image you see that there are two models: Collections and SequenceableCollection, and SequeanceableCollection is selected to be the current one of the analysis.
How can I access to that model if I am coding any property in a class? I checked the entities to know if each entity knows the model which belongs to, but it seems not.
In the long past we could do ModelManager uniqueInstance currentModel, but now, how do I know that information?
I am using Pharo version. I used the VW version during the weekend, but it seems that there are some code broken and I could not manage to make it work.
Cheers,
Gabi
2010/4/12 Tudor Girba tudor.girba@gmail.com Hi Gabi,
Nice to hear from you :).
ModelManager was replaced by just another Model that holds Models. To get to it, you do "MooseModel root" and if you want to see allModels from there, you do "MooseModel root allModels".
Yes, properties are defined using pragmas.
Which Moose are you using? Pharo or VW?
Cheers, Doru
On 12 Apr 2010, at 02:11, Gabriela Arevalo wrote:
Hi guys,
I have two basic questions regarding the implementation of Moose
- How do we manage now the currentModel (the selected Model in
the Moose UI)? A long time ago :) :), we have had the ModelManager class and we could do ModelManager uniqueInstance currentModel
- Properties: I have seen that we are using pragmas from the
instance side. Is it right? Or are there any other way of specifying them?
Cheers,
Gabi _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Beauty is where we see it."
-- www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Speaking louder won't make the point worthier."
On 12 avr. 2010, at 21:48, Tudor Girba wrote:
Hi,
This should not be the case. Every subclass of MooseEntity stores the mooseModel in the attribute dictionary from EntityState. Where did you notice the slowdown?
I dive into the code to check because it was the tip of the iceberg for issue 358. Actually the slowdown can only exist when creating new entities, before adding it to the model.
EntityState>>model computes lazily the moose model if necessary, but this can be very slow if many entities request mooseModel as #ownerOf: performs a scan of all mooseModels for each (to find the one containing the entity with the same mooseId).
EntityState>>model ^self attributeGet: #privateModel default: [MooseModel ownerOf: self entity]
Instead what happens is that adding an entity to a moose model automatically sets this attribute. MooseModel>>add: anElement
anElement privateSetMooseModel: self.
So correction: it may be slow if you request mooseModel at creation time (but usually you know the model at creation time).
Cheers, Doru
On 12 Apr 2010, at 21:38, Alexandre Bergel wrote:
Thanks Simon,
this info is important.
Cheers, Alexandre
On 12 Apr 2010, at 15:27, Simon Denier wrote:
Hi Gabi
Just from experience, if you send mooseModel to all entities in a large model, it can take a long time. So if you run into scalability problem, it may come from that. Now depending on your use case, there might be other solutions.
On 12 avr. 2010, at 19:57, Tudor Girba wrote:
Hi Gabi,
Ahh, now I understand. Any entity answers to mooseModel, so you can do:
FAMIXClass>>someMethod self mooseModel ...
Great that you are using the Pharo version. Just for convenience, you can find the latest development image here: http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/a...
Please let us know if you have further problems.
Cheers, Doru
On 12 Apr 2010, at 18:18, Gabriela Arevalo wrote:
Hi Doru,
Thanxs for answering so quick.
I am attaching an jpg to illustrate my problem :)
If I evaluate MooseModel root, I get an instance of MooseModel that contains all the existing models. In the image you see that there are two models: Collections and SequenceableCollection, and SequeanceableCollection is selected to be the current one of the analysis.
How can I access to that model if I am coding any property in a class? I checked the entities to know if each entity knows the model which belongs to, but it seems not.
In the long past we could do ModelManager uniqueInstance currentModel, but now, how do I know that information?
I am using Pharo version. I used the VW version during the weekend, but it seems that there are some code broken and I could not manage to make it work.
Cheers,
Gabi
2010/4/12 Tudor Girba tudor.girba@gmail.com Hi Gabi,
Nice to hear from you :).
ModelManager was replaced by just another Model that holds Models. To get to it, you do "MooseModel root" and if you want to see allModels from there, you do "MooseModel root allModels".
Yes, properties are defined using pragmas.
Which Moose are you using? Pharo or VW?
Cheers, Doru
On 12 Apr 2010, at 02:11, Gabriela Arevalo wrote:
Hi guys,
I have two basic questions regarding the implementation of Moose
- How do we manage now the currentModel (the selected Model in the Moose UI)?
A long time ago :) :), we have had the ModelManager class and we could do ModelManager uniqueInstance currentModel
- Properties: I have seen that we are using pragmas from the instance side. Is it right? Or are there any other way of specifying them?
Cheers,
Gabi _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Beauty is where we see it."
-- www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Speaking louder won't make the point worthier."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
That is better :)
Cheers, Doru
On 13 Apr 2010, at 00:29, Simon Denier wrote:
On 12 avr. 2010, at 21:48, Tudor Girba wrote:
Hi,
This should not be the case. Every subclass of MooseEntity stores the mooseModel in the attribute dictionary from EntityState. Where did you notice the slowdown?
I dive into the code to check because it was the tip of the iceberg for issue 358. Actually the slowdown can only exist when creating new entities, before adding it to the model.
EntityState>>model computes lazily the moose model if necessary, but this can be very slow if many entities request mooseModel as #ownerOf: performs a scan of all mooseModels for each (to find the one containing the entity with the same mooseId).
EntityState>>model ^self attributeGet: #privateModel default: [MooseModel ownerOf: self entity]
Instead what happens is that adding an entity to a moose model automatically sets this attribute. MooseModel>>add: anElement
anElement privateSetMooseModel: self.
So correction: it may be slow if you request mooseModel at creation time (but usually you know the model at creation time).
Cheers, Doru
On 12 Apr 2010, at 21:38, Alexandre Bergel wrote:
Thanks Simon,
this info is important.
Cheers, Alexandre
On 12 Apr 2010, at 15:27, Simon Denier wrote:
Hi Gabi
Just from experience, if you send mooseModel to all entities in a large model, it can take a long time. So if you run into scalability problem, it may come from that. Now depending on your use case, there might be other solutions.
On 12 avr. 2010, at 19:57, Tudor Girba wrote:
Hi Gabi,
Ahh, now I understand. Any entity answers to mooseModel, so you can do:
FAMIXClass>>someMethod self mooseModel ...
Great that you are using the Pharo version. Just for convenience, you can find the latest development image here: http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/a...
Please let us know if you have further problems.
Cheers, Doru
On 12 Apr 2010, at 18:18, Gabriela Arevalo wrote:
Hi Doru,
Thanxs for answering so quick.
I am attaching an jpg to illustrate my problem :)
If I evaluate MooseModel root, I get an instance of MooseModel that contains all the existing models. In the image you see that there are two models: Collections and SequenceableCollection, and SequeanceableCollection is selected to be the current one of the analysis.
How can I access to that model if I am coding any property in a class? I checked the entities to know if each entity knows the model which belongs to, but it seems not.
In the long past we could do ModelManager uniqueInstance currentModel, but now, how do I know that information?
I am using Pharo version. I used the VW version during the weekend, but it seems that there are some code broken and I could not manage to make it work.
Cheers,
Gabi
2010/4/12 Tudor Girba tudor.girba@gmail.com Hi Gabi,
Nice to hear from you :).
ModelManager was replaced by just another Model that holds Models. To get to it, you do "MooseModel root" and if you want to see allModels from there, you do "MooseModel root allModels".
Yes, properties are defined using pragmas.
Which Moose are you using? Pharo or VW?
Cheers, Doru
On 12 Apr 2010, at 02:11, Gabriela Arevalo wrote:
Hi guys,
I have two basic questions regarding the implementation of Moose
- How do we manage now the currentModel (the selected Model in
the Moose UI)? A long time ago :) :), we have had the ModelManager class and we could do ModelManager uniqueInstance currentModel
- Properties: I have seen that we are using pragmas from the
instance side. Is it right? Or are there any other way of specifying them?
Cheers,
Gabi _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Beauty is where we see it."
-- www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Speaking louder won't make the point worthier."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Some battles are better lost than fought."
-
Alexandre Bergel -
Simon Denier -
Tudor Girba