Package nz.org.riskscape.hdf5.types

Class H5IntegerType

java.lang.Object
nz.org.riskscape.hdf5.H5Object
nz.org.riskscape.hdf5.types.H5Type
nz.org.riskscape.hdf5.types.H5IntegerType
All Implemented Interfaces:
AutoCloseable
public class H5IntegerType extends H5Type

  • Constructor Details

    • H5IntegerType

      protected H5IntegerType(long id, boolean opaqueUnsignedLongs)

    • H5IntegerType

      protected H5IntegerType(long id)

  • Method Details

    • isUnsigned

      public boolean isUnsigned()

    • intToBytes

      public byte[] intToBytes(long value)

    • read

      public Object read(ByteBuffer outBuf, int offset)
      Specified by:
      read in class H5Type
      Returns:
      a java object that represents the data that was stored in the outBuf if it was of this data type. This java object should be coercable in to the type returned from H5Type.toType()

    • toString

      public String toString()
      Specified by:
      toString in class H5Type

    • toType

      public nz.org.riskscape.engine.types.Type toType()
      Specified by:
      toType in class H5Type
      Returns:
      a Riskscape type that mirrors the HD5 data type

    • isVariableLength

      public boolean isVariableLength()
      Specified by:
      isVariableLength in class H5Type
      Returns:
      true if this type is, or contains something, of variable length. As yet, this H5 support in this plugin can not read datasets of variable length type

    • setOpaqueUnsignedLongs

      public void setOpaqueUnsignedLongs(boolean opaqueUnsignedLongs)

      As a performance optimisation, we can read a 64 bit unsigned long as a signed long, to avoid having to use BigIntegers. As long as the data never exceeds Long.MAX_VALUE or not used as a number then this is safe to do an can give a massive speed up.

      Because this gives a potential loss of functionality, it is off by default.

      Setting this mutates the type instance, so make sure you 'own' the data type before setting it.

    • isOpaqueUnsignedLongs

      public boolean isOpaqueUnsignedLongs()

      As a performance optimisation, we can read a 64 bit unsigned long as a signed long, to avoid having to use BigIntegers. As long as the data never exceeds Long.MAX_VALUE or not used as a number then this is safe to do an can give a massive speed up.

      Because this gives a potential loss of functionality, it is off by default.

      Setting this mutates the type instance, so make sure you 'own' the data type before setting it.