Hi,
Hi Mariano,
For some reason your mail appeared as blocked for the mailing list.
I undid the setting now.
Weird...Moose doesn't like me :(
Let's not jump to conclusions :). This probably happened because the
mail address rejected the mails from this mailing list or something
like that. Although this is strange because it's gmail.
Did you get the previous email of Simon?
Yes, but I guess because he put me in cc.
He did not add you in cc, and neither did I. So, it works now :).
Cheers,
Doru
Thanks
Mariano
Cheers,
Doru
On 25 May 2010, at 14:35, Simon Denier wrote:
On 25 mai 2010, at 14:06, Mariano Martinez Peck wrote:
Hi Moosers. I am doing little experiments to export/serialize big
graph of objects using ImageSegment. I though that MooseModel was a
good candidate. And I even remember Simon's wishes for copying them.
But I have a couple of questions:
1) Which is the bigger autogenerated MooseModel I can get to test?
For the moment I am evaluating "MooseModel installDefaultModels".
and then I export "MooseModel root". Is there a bigger one I can
use? how ?
Take a look at the MooseScripts class, class-side. There are a
number of methods to create moose models from the image itself. In
order of importance: Network << Moose << Pharo
With network, you won't have any problem. With a model of Moose
itself, it's fast enough to do lots of test yet you can still
improve things. Then a Pharo model is certainly a good scalability
test.
2) How is the root or any other MooseModel normally exported? Which
methods? which technology ? Can you give me an example of the
standard way to export/serialize/copy a MooseModel ? The only thing
I saw is MooseModel class >> export: aModel to: aStream
I just open a file and send it as Stream?
Depends...
- File persistency is done in the MSE format and using Fame to
serialize entities in MSE.
Just take a look at MooseModel>>exportToMSEStream:
- To clone a model, just use MooseModelCopier>>copyModel: (this was
a simple experiment to make practical copies of large MooseModels.
Or rather to show that simple copy did not scale well on large
MooseModel right now).
3) Suppose that I copy/export somehow a MooseModel (suppose the
root) to a file. I take another Moose image, I load the file,
objects are alive again and I replace MooseModel rootModel with the
new object. How do I know if the copy/export worked correctly ?
If I do it in the same image, I can have both, but how can I compare
them to be sure everything was done ok ? method #= has no sense as
it will use Object with is #==. So...any idea to know if the
MooseModel I export and load again with ImageSegment is really
working or not?
I would change the tests setup to export/import the test model and
run tests on it (that's what I did to test the MooseModelCopier).
Only problem is that tests use some small models, so maybe some
things will be hidden. This is start though.
I want to test exporting and loading these MooseModel with different
technologies but I need a way to know if the resulted object is
correct or not.
Ahhh please, cc' me in the mail as I am not sure I receive emails
from this list.
Thanks for any hints.
Mariano
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Being happy is a matter of choice."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot
be done."