[Moose-dev] Re: usage of moose and easel

Currently, CSV tables are not hooked into Moose. I have no idea if someone has worked on this or not. On my side, I have never hooked CSV table to Moose because I have never seen a need for this. Consider the following script: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= |tab ds b | tab := RTTabTable new input: 'http://earthquake.usgs.gov/earthquakes/feed/v0.1/summary/2.5_month.csv' asUrl retrieveContents usingDelimiter: $,. tab removeFirstRow. tab replaceEmptyValuesWith: '0' inColumns: #(4 5). tab convertColumnsAsFloat: #(4 5). b := RTGrapher new. ds := RTDataSet new. ds interaction popup. ds points: tab values. ds dotShape color: (Color blue alpha: 0.3). ds x: [ :row | row at: 4 ]. ds y: [ :row | row at: 5 ]. b add: ds. b maxY: 8. b maxX: 700. b axisX title: 'depth'. b axisY title: 'magnitude'. b build. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= It visualizes seisms in plain Roassal, without the need to have it hooked into moose. This is a singular example. If I would deal with Seisms the all day long, then yes, I would surely hook it into moose (e.g., extending the Moose meta model, adding an importer in the Moose Panel, …). At that stage, I have never seen the need. Do you really need to keep all the cells at the same time? If this is the case, when you will probably need to work on the way to approach this case study. Several ways are possible: - You can use fuel to load and unload part of the CSV table on the disk. This should not be difficult at all. - You can keep in the image only the index of the CSV row, and access to it when you wish to get more data from it. I am sure there are other way to deal with such a large file. It all depends on what the file contains. Again, this is something that is not difficult to do. Which kind of calculation? You can either use OpenCL or span other images. Again, we have solution for this. For example, feel free to get in touch with Juan Pablo Sandoval, my PhD student. He has worked quite a lot on spanning new images. Roassal is indeed becoming slow when you reach around ~ 400 000 elements on screen. This is not really a surprise because there is no optimization. However, all is made to hook strategy for large amount of data. Yes, all within Pharo. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.