20 Jul
2009
20 Jul
'09
7:14 p.m.
Unfortunately, it is not quite loadable in the default Moose because
the Pharo MSE is based on FAMIX 3.0 and it uses the new MSE format
(due to Fame).
However, it can possibly be loaded using the FAMIX 3.0 (although it
can possibly be a bit out of date) implementation form VW.
Doru
On 20 Jul 2009, at 18:59, Michele Lanza wrote:
This is cool. Did you try to load the mse into a
VW-moose? For once
some techniques that were developed could be applied on a "living"
large piece of source code with a real need for understanding and
problem finding.
Cheers
Michele
On 20-Jul-09, at 4:36 PM, Laval Jannik wrote:
--
www.tudorgirba.com
"Problem solving should be concentrated on describing
the problem in a way that is relevant for the solution."
Hi all,
For information:
I have made a pharo.mse (available in
http://www.jannik-laval.eu/assets/files/softAnalysis/mseFiles/)
.
First, I have imported Pharo in moose. For this, I run the VM with
the
option "-memory 1500m". The time to load pharo in moose: 2 days.
(pharo.image size: 822 Mo)
Next, I have extract the pharo model in mse. It takes a lot of time
(near 4 days).
Now, in a new pharo image with default parameter of the vm, it is not
possible to load the mse. I think there is not enough memory.
I think all these methods could be optimized.
Cheers
---
Jannik Laval
PhD Student - Rmod Team - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.eu
http://rmod.lille.inria.fr
---
_______________________________________________
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