public interface DataStore
DataSpec
object
is also required.
Because instances of this class manage the data, by keeping track of
the DataStore
s in an application you can control where
the memory is used. All the other objects connected with a plot,
for instance the PlotLayer
s
and DataSpec
s, are cheap
to produce and have small memory footprints, so can be created and
destroyed as required.
As a rule therefore, DataStore objects should be managed by a single class,
and references not kept to them by any other potentially long-lived objects.
This class also contains a TupleRunner, which manages how TupleSequences acquired from it are used. Although the TupleRunner is not part of the stored data, it is always used in the same places as a DataStore, so it is convenient to carry it around in the same object.
Obtain an instance of this class from a DataStoreFactory
.
Modifier and Type | Method and Description |
---|---|
TupleRunner |
getTupleRunner()
Returns an object that manages iteration over tuples.
|
TupleSequence |
getTupleSequence(DataSpec spec)
Returns the data described by a given DataSpec as a sequence of
tuples.
|
boolean |
hasData(DataSpec spec)
Indicates whether this store has the data described by a given
DataSpec.
|
boolean hasData(DataSpec spec)
spec
- plot data specification objectTupleSequence getTupleSequence(DataSpec spec)
hasData(uk.ac.starlink.ttools.plot2.data.DataSpec)
returns true for the
given DataSpec; if not, behaviour is undefined.spec
- plot data specification objectTupleRunner getTupleRunner()
Copyright © 2025 Central Laboratory of the Research Councils. All Rights Reserved.