Comments (22)
Too general. Porting on a case-by-case
Reported by simon.denier
on 2009-07-15 12:52:13
- Status changed:
Closed
from moose.
Reported by tudor.girba
on 2009-07-24 13:04:08
- Status changed:
Fixed
from moose.
Reopened
Reported by simon.denier
on 2009-09-20 19:05:01
- Status changed:
Started
from moose.
Issue 165 has been merged into this issue.
Reported by simon.denier
on 2009-09-20 19:06:39
from moose.
Reported by tudor.girba
on 2009-09-20 20:35:22
- Labels added: Milestone-4.1
from moose.
Reported by simon.denier
on 2009-09-22 08:34:57
- Labels added: Component-Algos
from moose.
Reported by simon.denier
on 2009-12-03 13:25:40
- Labels added: Type-Project
- Labels removed: Type-Todo
from moose.
Are you referring to the SCG-Algorithm package in SCGStore?
The last version (1.28) essentially contains algorithm related to FCA. Is what you're
referring too?
Reported by alexandre.bergel
on 2010-02-23 21:34:52
from moose.
Partly yes. Actually it's anything related to algorithmic, which could be reused for
analysis. We should make a list
of what is available on the store. Cyrille just started to look at the packages for
Clustering and Serialization used
in distribution map.
Reported by simon.denier
on 2010-02-23 22:04:38
from moose.
=> There is The SCG-Algorithm bundle
-> essentially contains the package FormalConceptAnalysis (that we should port
to pharo )
=> There is the HapaxDevelopment bundle, which contains:
-> Clustering package (already port to Pharo (?))
-> LinearAlgebra package (already port to Pharo (?))
then
-> InformationRetrieval , according the moose website, we should port it
then
=> A lot of other packages (LinearAlgebra (more), HapaxVectorSpace , HapaxSemantic
,
HapaxTrendDetection , HapaxExamples , HapaxTest ) for wich I don't know if we have
to port them.
Reported by cy.delaunay
on 2010-02-24 12:30:40
from moose.
Let's say that Clustering and LinearAlgebra have been "converted" to Pharo, that is
exported from VW as
changeset (following the SCG procedure) then dumped in Pharo, with hacks in the changeset
so that Pharo
does not complain/crash because of the platform change (I dont remember the details,
but there is annoying
things there). For now it is not compatible with Pharo, and actually it crashes the
VM when tests are run, which
I find amazing.
For the other parts: FormalConceptAnalysis would be nice, but I thought that Andy Kellens
and Gabriela
would like to redo that too. We have to check with them.
InformationRetrieval sounds nice, I don't know what's behind but I guess that Adrian
K knows.
LinearAlgebra should perhaps be done in one pass, or at least converted in one pass.
All things related to
Hapax... I would be glad but perhaps that's a lot of work. We should ask Adrian Kuhn
and use our tools to
identify the most common parts to be retrieved.
Other things?
Reported by simon.denier
on 2010-02-24 13:17:27
from moose.
Tests from clustering and linearAlgebra no longer crash the VM. In fact, I just found
an infinite loop in the code,
removed it, and now tests runs but don't freeze the image.
I have also 'converted' FormalConceptAnalysis to pharo and save it in the MooseAlgos
squeaksource repository.
Reported by cy.delaunay
on 2010-02-24 13:42:06
from moose.
I have ported the package InformationRetrieval. All tests are green in pharo. I saved
it in the MooseAlgos
squeaksource repository. Let's look at the tests of LinearAlgebra ;)
Reported by cy.delaunay
on 2010-02-26 13:24:07
from moose.
All tests green for LinearAlgebra excepted for the class:
- MAFloatVectorTest. A primitive fail and I don't really know how to debug that.
Reported by cy.delaunay
on 2010-03-01 13:35:23
from moose.
Great work.
Reported by tudor.girba
on 2010-03-01 14:17:14
from moose.
All tests green for Clustering
Reported by cy.delaunay
on 2010-03-02 10:24:46
from moose.
Reported by simon.denier
on 2010-03-02 16:55:36
from moose.
Condition for closing this bug: all tests green. Further bug should be addressed as
they appear
Reported by cy.delaunay
on 2010-04-01 14:51:55
from moose.
I moved this item to 4.0, since it is now basically what requests #357
Reported by simon.denier
on 2010-04-06 18:31:41
- Labels added: Milestone-4.0
- Labels removed: Milestone-4.1
from moose.
Issue 357 has been merged into this issue.
Reported by simon.denier
on 2010-04-06 18:32:30
from moose.
All tests are now green.
I don't really know what was the use of MAFloatVector in VisualWorks, but when looking
to the code, it seems
that its specificity is just to store Floats.
The error came from the way floats were stored in VisualWorks or something related
to that.
The solution I provided is to implement MAFloatVector as MAArrayVector (which works
well), and just convert
elements asFloat before storing them. If this is really the only thing it should do,
it seems to works, and all tests
are green.
Reported by cy.delaunay
on 2010-04-07 09:35:22
from moose.
It seems ok, but you should post something about that on the Pharo list. Perhaps some
people will have better
knowledge of the primitives concerned.
Reported by simon.denier
on 2010-04-08 09:31:46
- Status changed:
Fixed
- Labels added: Platform-Pharo
- Labels removed: Platform-Squeak
from moose.
Related Issues (20)
- Remove GT methods from Moose HOT 2
- defaultSpec used as defaultLayout HOT 3
- centralize all Moose CI results on a web page
- Cannot inspect FamixPackageGroup in Moose
- Add model validation
- Change Github Action to update release HOT 1
- [Merlin] Use of non-existent class PluggableTextFieldMorph HOT 1
- [Merlin] MerlinExamples not working HOT 2
- Moose 10 template includes wrong Pharo version HOT 8
- Add Moose11 in smalltalk CI HOT 1
- Dependency issue in Baseline for MooseHelp ? HOT 1
- Incorrect display of SourceText when source file contains Emojis HOT 1
- Add google search textfield to modularmoose.org site HOT 1
- #sort: on MooseGroup not working HOT 8
- Number of Model entities not coherent between QueryBrowser and Inspector HOT 3
- Move remaining code to MooseIDE
- How to offer generic queries/issues ?
- correct selector #atOrOrederedCollection: in Dictionary
- [API Request] conditionnal add: on MooseAbstractGroup (and FMSlotMultivalueLink)
- StInspector(Object)>>doesNotUnderstand: #isMiBrowser HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from moose.