ch.systemsx.cisd.openbis.plugin.screening.shared.api.v1.dto.ImageDatasetMetadata.getChannelLabels()
|
ch.systemsx.cisd.openbis.plugin.screening.shared.api.v1.dto.ImageDatasetMetadata.getChannelNames()
|
ch.systemsx.cisd.openbis.plugin.screening.client.api.v1.IScreeningOpenbisServiceFacade.getDataSets(PlateIdentifier, String)
|
ch.systemsx.cisd.openbis.plugin.screening.client.api.v1.IScreeningOpenbisServiceFacade.getDataSets(WellIdentifier, String)
|
ch.systemsx.cisd.openbis.plugin.screening.shared.api.v1.dto.FeatureVectorDataset.getFeatureNames() |
ch.systemsx.cisd.openbis.plugin.screening.client.api.v1.IScreeningOpenbisServiceFacade.listAvailableFeatureNames(List extends IFeatureVectorDatasetIdentifier>)
Use IScreeningOpenbisServiceFacade.listAvailableFeatureCodes(List) instead. Since version 1.2 of the
API features are no longer identified by a name but by a code. Previous client
code still works but the name will be normalized internally. "Normalized" means
that the original name argument is converted to upper case and any symbol which
isn't from A-Z or 0-9 is replaced by an underscore character. The
FeatureVectorDataset will provide feature codes and feature labels.
|
ch.systemsx.cisd.openbis.plugin.screening.client.api.v1.IScreeningOpenbisServiceFacade.listImageDatasets(List extends PlateIdentifier>)
|
ch.systemsx.cisd.openbis.plugin.screening.client.api.v1.ScreeningOpenbisServiceFacade.listImageDatasets(List extends PlateIdentifier>)
|
ch.systemsx.cisd.openbis.plugin.screening.client.api.v1.IScreeningOpenbisServiceFacade.loadFeaturesForPlateWells(ExperimentIdentifier, MaterialIdentifier, List)
|
ch.systemsx.cisd.openbis.plugin.screening.client.api.v1.IScreeningOpenbisServiceFacade.loadFeaturesForPlateWells(MaterialIdentifier, List)
|