MSE models repository
by Andrea Caracciolo
Hi folks,
At the following address you will find a repository of MSE files derived from the Qualitas Corpus:
=> http://scg.unibe.ch/pangea/
The purpose of this repository is providing a common and easy to setup dataset for (moose-based) analyses.
The files can be freely downloaded and used.
The repository has the following structure:
- QualitasCorpus
- yyyymmdd(e | r): qualitas corpus with MSE files
- yyyymmdd(e | r)-compressed: original qualitas corpus (as downloaded from http://qualitascorpus.com/)
- extractor: tool used to generate MSE files (verveineJ SVN rev. 192)
- mse: generated MSE files
- scripts: shell script for setting up the analysis data folder
How to setup the analysis data folder ?
1. download all files available at http://scg.unibe.ch/pangea/scripts/
2. chmod +x
3a. ./fetchQCr.sh for downloading and uncompressing Qualitas Corpus "recent release" + MSE files
3b. ./fetchQCe.sh for downloading and uncompressing Qualitas Corpus "evolution release" + MSE files
at the end you should have an exact clone of http://scg.unibe.ch/pangea/QualitasCorpus/20120401r/ and/or http://scg.unibe.ch/pangea/QualitasCorpus/20120401e/
How to run an analysis ?
Use a script like this>
-----------------------------------------------
cog="path/to/CogVM"
moose="path/to/moose.image"
smalltalk="path/to/SmallTalkCode.st"
for m in $(find . -name 'model.mse'); do
src=${m/model.mse/src}
ln -s $m model.mse # link to model file
ln -s $src src # link to src file
$cog -nodisplay $moose $smalltalk
rm model.mse
rm src
done
-----------------------------------------------
where SmallTalkCode.st is something like>
-----------------------------------------------
| stream model |
model := MooseModel new.
stream:= MultiByteFileStream newFrom:(FileStream readOnlyFileNamed: 'model.mse').
model name:(FileDirectory baseNameFor: stream localName).
model importFromMSEStream: stream.
model size > 0 ifTrue: [ model install ].
model rootFolder:'src'.
"… analysis ..."
WorldState addDeferredUIMessage: [ SmalltalkImage current snapshot: false andQuit: true ].
-----------------------------------------------
Andrea
11 years
Issue 827 in moose-technology: Strange popupView in Roassal
by moose-technology@googlecode.com
Status: New
Owner: alexandr...(a)gmail.com
Labels: Type-Defect Priority-Critical Component-Roassal
New issue 827 by alexandr...(a)gmail.com: Strange popupView in Roassal
http://code.google.com/p/moose-technology/issues/detail?id=827
The popupView: behaves oddly. Consider the following script:
| view |
view := ROMondrianViewBuilder new.
view interaction popupView: [ :el :myView |
myView shape rectangle fillColor: Color yellow.
myView node: 20 forIt: [
myView shape rectangle fillColor: Color blue.
myView node: 30
].
myView horizontalLineLayout.
myView applyLayout
].
view shape rectangle size: 40.
view node: 10.
view open
11 years
Issue 826 in moose-technology: Roassal hover popup on edges
by moose-technology@googlecode.com
Status: New
Owner: alexandr...(a)gmail.com
Labels: Type-Defect Priority-High Component-Roassal
New issue 826 by alexandr...(a)gmail.com: Roassal hover popup on edges
http://code.google.com/p/moose-technology/issues/detail?id=826
With the following script, in Mondrian when you hover over edges a popup
appears showing the name of the edge. Is the same possible with Roassal?
view shape rectangle size: 20.
nodes := view nodes: (1 to: 20).
view edges: (2 to: 20) from: 1 to: #yourself.
view circleLayout.
Thanks Ben for noticing this!
11 years