Re: [science-iwg] Eclipse Datasets for Science

[Ian Mayo <ian@xxxxxxxxxxxxx>]

Morning Tracy & Jonah,
thanks for putting in this effort.

>  When you next have an opportunity we hope all interested parties could
>  1.Try it out
>    - can you run the example?

I can report that the Getting Started steps on the examples repo page
[1] worked fine for me.  BasicExample ran without warnings, but the
other examples complained about the lack of an slf4j binding [2]
(though the unit tests passed).

>    - can you integrate it with your codebase?

I don't have a codebase (yet), so can't help there.

>  2. Get Involved in architecture discussions:
>    - how does it fit within your framework?

n/a

>    - what works well?

n/a

>    - what's missing?

* From the DAWN code, I think there is value in the IOperation
framework being pulled over. The IOperation classes appear
implementation agnostic - so it should be possible to add generic
operations to this project for common use.

>    - suggestions for improvements.

* It would seem fairly straightforward to introduce TimeDataset and
PeriodDataset classes to store instants in time and periods of elapsed
time respectively.  Representing time and period in dedicated classes
offers the opportunity for the respective APIs to provide additional
methods (e.g. before, after, overlaps). Dedicated classes also reduces
the chance of integration troubles caused by teams misunderstanding
how, for example, an elapsed period is being represented in a
DoubleDataset (one team presumes floating point seconds, another team
presumes floating point millis).

* Deeper support for data change listeners will allow the UI to update
when data changes, or for a chain of dependent datasets & operations
that dynamically update on changes to precedent datatset.

* I accidentally conflated the MetadataType and IMetadata types
handled by ILazyDataset & IDataset whilst familiarising myself with
the code.    Since IMetadata actually is an instance of MetadataType,
I guess my confusion would be avoided by removing getMetadata() from
IDataset (replacing it with getMetadata(IMetadata.class).

* As Peter Chang suggested in email yesterday, it may be worth
removing the ROI classes - since these seem specific to one usage of
IDataset.  Other applications/domains will have their own libraries of
geometric shapes (such as the JTS libraries used in GeoTools [3])

Cheers,
Ian


[1] https://github.com/jonahkichwacoders/org.eclipse.dataset.examples#getting-started
[2] http://pastebin.com/raw.php?i=PeYGxRp1
[3] http://docs.geotools.org/stable/userguide/library/jts/index.html

On 8 September 2015 at 23:27, Tracy Miranda <tracy@xxxxxxxxxxxxxxxx> wrote:
> Following on from our previous email[1] Jonah has now created a fork of
> DAWNSci's datasets which is available here:
> https://github.com/jonahkichwacoders/org.eclipse.dataset
>
> Details of how you can try it out for yourself are here:
> https://github.com/jonahkichwacoders/org.eclipse.dataset.examples
>
> In particular this fork:
> * Is a subset of dataset functionality
> * Has a p2 site available to try out the code
> * p2 site includes source bundles
> * Depends only on current Orbit approved bundles
> * Has no pre-compiled JARs
> * Works with Eclipse 4
> * Works as a standalone JAR
> * Includes all relevant tests from Dawn
> * Buildable with maven/tycho (e.g. run mvn verify and get an update site)
> * using Travis CI as build machine
>
> Datasets features & functionality includes:
>   * Various types: doubles, compound, complex, float, etc
>   * Array creation
>   * Universal functions e.g. sin, cos, exp
>   * Linear algebra
>   * Indexing & slicing
>   * Regions of interest e.g. rectangular
>
> This fork is intended to be a springboard for SWG members to try out DAWN
> datasets, and start to discuss how it applies to their projects. We will
> maintain it in the short term.
>
>   When you next have an opportunity we hope all interested parties could
>   1.Try it out
>     - can you run the example?
>     - can you integrate it with your codebase?
>
>   2. Get Involved in architecture discussions:
>     - how does it fit within your framework?
>     - what works well?
>     - what's missing?
>     - suggestions for improvements.
>
> Ultimately the goal is to have a standardised dataset API & implementation
> shared by all.
>
> Regards,
> Tracy
>
> [1] http://dev.eclipse.org/mhonarc/lists//science-iwg/msg01074.html
>
> _______________________________________________
> science-iwg mailing list
> science-iwg@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/science-iwg



-- 
Ian Mayo
Deep Blue C Technology Ltd
- New technologies, implemented well