To a unified software model repository for Moose.
Locked
123
123
Re: To a unified software model repository for Moose.
 
|
We have benchmarks for Fuel and MSE. However, I was just trying to run the benchs with MSE (to compare to Fuel) but I run into the attached problem.
It seems related to FAMIX, but I have no idea. If someone can fix it, I can finish the benchmark.
Mariano http://marianopeck.wordpress.com _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
mseMoose.txt (40K)
Re: To a unified software model repository for Moose.
|
|
Re: To a unified software model repository for Moose.
|
|
Re: To a unified software model repository for Moose.
|
|
Re: To a unified software model repository for Moose.
|
|
Re: To a unified software model repository for Moose.
|
|
Re: To a unified software model repository for Moose.
|
|
Re: To a unified software model repository for Moose.
|
|
Re: To a unified software model repository for Moose.
|
|
Re: To a unified software model repository for Moose.
|
|
Re: To a unified software model repository for Moose.
|
|
In reply to this post by Mariano Martinez Peck
Hi Mariano,
Could you please share the scripts you used for the benchmark? I attach here the one I use. Cheers, Doru On Fri, Jul 27, 2012 at 4:39 PM, Mariano Martinez Peck <[hidden email]> wrote: > > > On Fri, Jul 27, 2012 at 4:19 PM, Mariano Martinez Peck > <[hidden email]> wrote: >>> >>> >>> >>> Would it make sense to distribute also a FUEL file containing the famix >>> model ? >>> Would it make loading faster ? >>> >> >> We have benchmarks for Fuel and MSE. However, I was just trying to run the >> benchs with MSE (to compare to Fuel) but I run into the attached problem. >> It seems related to FAMIX, but I have no idea. If someone can fix it, I >> can finish the benchmark. >> > > So the benchmarks for The model network and morphic are: > > Model name: Morphic > Model size: 110798 > > MSE export: 219031 ms > MSE import: 25331 ms > MSE file size: 13135561 bytes > > FL export: 8492 ms > FL import: 5118 ms > FL file size: 4805120 bytes > > Fuel export is a 4% of MSE export. > Fuel import is a 20% of MSE import > Fuel file size is a 36% of MSE file size > > ------- > > Model name: Network > Model size: 26949 > > MSE export: 49283 ms > MSE import: 4889 ms > MSE file size: 3144945 bytes > > FL export: 1788 ms > FL import: 1049 ms > FL file size: 1219372 bytes > > Fuel export is a 4% of MSE export. > Fuel import is a 21% of MSE import > Fuel file size is a 38% of MSE file size > > So the difference between both models are quite proporcional :) > > Cheers, > > >> >> >> >>> >>> > >>> > Jannik >>> > >>> >> >>> >>> It could contains all the informations that we discussed here. >>> >>> >>> >>> Jannik >>> >>> >>> >>> >>> >>> >>> >>>> Andrea >>> >>>> >>> >>>> >>> >>>> >>> >>>> _______________________________________________ >>> >>>> Moose-dev mailing list >>> >>>> [hidden email] >>> >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >>> >>> --- >>> >>> Jannik Laval >>> >>> >>> >>> >>> >>> _______________________________________________ >>> >>> Moose-dev mailing list >>> >>> [hidden email] >>> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >> >>> >> >>> >> _______________________________________________ >>> >> Moose-dev mailing list >>> >> [hidden email] >>> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> > >>> > --- >>> > Jannik Laval >>> > >>> > >>> > _______________________________________________ >>> > Moose-dev mailing list >>> > [hidden email] >>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > > -- > Mariano > http://marianopeck.wordpress.com > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > -- www.tudorgirba.com "Every thing has its own flow" _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: To a unified software model repository for Moose.
|
|
Re: To a unified software model repository for Moose.
|
|
Re: To a unified software model repository for Moose.
|
|
Re: To a unified software model repository for Moose.
|
|
Hi Jannik,
Are you saying that this feature can't be added because some already implemented actions are not always working as expected ? Did i understand correctly ? Do you think you can fix it ? Do you need help with it ? I attached a small code snippet which might help developing a possible solution… Andrea On Jul 30, 2012, at 9:32 PM, jannik.laval wrote: > Dear Andrea, > > I am happy that you try to use Orion. > The primary goal of Orion was to try modifications on a model and keep changes. > > The meta-model allows clearly to save history, but the infrastructure needs some work. > For now, a diff is not implemented. We have to think about this feature. I have no idea how to do that, because some problems appear when merging or forking. > > Jannik > > > On Jul 30, 2012, at 11:41 AM, Andrea Caracciolo <[hidden email]> wrote: > >> I downloaded the latest version from OrionDev and i tried to create 2 model versions starting from 2 MSE files of two subsequent versions of the same project. >> >> The following code does simply create 2 versions, the second of which contains all the entities coming from famixModel2 and a reference to all the entities contained in model1. >> >> model1 := OrionConverter convertFrom: famixModel1. >> model2 := OrionConverter convertFrom: famixModel2. >> system originalModel: model1. >> model1 orionSystem: system. >> model2 withParent: model1. >> >> I would like to know if there is a method which allows to add a new version and also makes a diff between the entities being added and the entities contained in the parent version. >> The diff should be made between entities sharing the same mooseName and should be done on the basis of the contained code (if existing). >> >> Thanks :) >> >> On Jul 28, 2012, at 10:17 PM, jannik.laval wrote: >> >>>>> >>>>> >>>>> If there are multiple versions of a project, it would be also interesting to distribute an Orion model of all the versions. >>>>> Is it possible to build such a model having an MSE file for each version as input ? >>>> >>>> yes >>>>> How much effort is needed to fix the bugs and make it work ? >>>> >>>> Jannik? But normally it should work. >>> >>> Iep, it should work. >>> I used the pragma for importing elements in MSE. >>> But I never tried it. >>> >>>> Now I do not know if orion covers all the famix entities but extending it should not be a problem, >>> >>> It is easy and fast to extend FAMIX entities. >>> >>> Jannik >>> >>>> What would be good is that orion gets the trick that andy and veronica implemented in their implementation of Orion >>>> >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > --- > Jannik Laval > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: To a unified software model repository for Moose.
|
|
Re: To a unified software model repository for Moose.
|
|
Re: To a unified software model repository for Moose.
|
|
Re: To a unified software model repository for Moose.
|
|
| Free forum by Nabble | Edit this page |