Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The analytical clients provide for client-side caching of Synapse files, to avoid unnecessarily retrieving (large or many) files that are already available locally.  When a file is uploaded or downloaded the client keeps track of the location along with information to determine if it is later changed.  Specifically, the client maintains a "Cache Map" whose keys are local file locations and whose values are UTC last-modified-on times.  The use of this map is as follows: 

Case

Action

synStore is called to upload a new file to Synapse.A new entry is made in the Cache Map.

synStore is called to upload a File object which has already been uploaded to Synapse.

(i.e. same name, Synapse ID, file path, parent, etc.)

  1. The associated 'last modified' time in the File Cache is compared to the 'last modified' time for the file. 
  2. If the timestamps are the same no upload occurs. 
  3. Otherwise the file is uploaded (generating a new FileHandle ID) 
  4. A new Cache Map entry is created with the FileHandleID and timestamp. 

The old entry is left in place, since some other in-memory File object may reference the same local file.

synGet is called for a File object which has not been downloaded locally.
  1. The File metadata are retrieved, including the FileHandleID.
  2. Since there is no entry in the Cache Map, the file is downloaded and an entry made in the Cache Map.
synGet is called for a File object which has been downloaded locally with a different target location.
  1. The File metadata are retrieved, including the FileHandle ID.  
  2. An entry is found in the Cache Map for the given FileHandle ID, but not for the given location. 
  3. If any currently downloaded file in the Cache Map for the FileHandle ID has an unchanged 'last modified' timestamp, it is copied to the new location.
  4. Otherwise, the file is downloaded from Synapse to the new location.  
  5. A new Cache Map entry is created for the new file.  

We do NOT make the new File object point to the cached file, since unexpected behavior would result when multiple File objects modify the same on-disk file.

synGet is called for a File object which has been downloaded locally with the same target location.
  1. The File metadata are retrieved, including the FileHandle ID.   
  2. An entry is found in the Cache Map for the given FileHandle ID and location.  
  3. If the cached timestamp matches the 'last modified' timestamp for the file, no download occurs. 
  4. If the local file is *missing*, then the file is downloaded.  
  5. Otherwise, the action depends on the "ifcollision" mode specified for synGet:  
    1. "overwrite.local":  The file is downloaded to the target location and the Cache Map entry is updated with a new timestamp;
    2. "keep.local":  No download occurs.  The File references the locally modified file at the given location;
    3. "keep.both":  The file is downloaded to the target location, but given a modified local file name.  A second entry for the FileHandle ID is made in the Cache Map.

Cache Location

When a file is downloaded, specifying the file location is optional.  By default, the file is placed in a cache folder along with a Cache Map file.  

...

We conceptual divide the client commands into three levels (1) Common functions, (2) Advanced functions and (3) low-level Web API functions.  The first collection of commands captures the majority of functionality of interest to users. The second collection rounds out the functionality with less frequently used functions.  The third set comprises simple, low level wrappers around the Synapse web service interface.  By including this third set users can access web services in advance of having specialized commands in the analytic clients.

 

Command

comments

R Syntax

Python Syntax

Command Line Syntax

1 – Common functions

    

Create a Synapse file handle in memory, specifying the path to the file in the local file system, the name in Synapse, and the Folder in Synapse.  This step 'stages' a file to be sent to Synapse. Additional parameters (...) are interpreted as properties or annotations, in the manner of synSet(), defined below.  If 'synapseStore' is TRUE then file is uploaded to S3, else only the file location is saved.

Note:  synapseStore=T is not allowed if "path" is a URL rather than a local file path.

The specified file doesn't move or get copied.

File(path, parentId, synapseStore=T, ...)

 

example:

File(path="/path/to/file", parentId="syn101")

File(path, parentId, synapseStore=True, **kwargs)

 

example:

File('/foo/baz/bar.txt', 'syn123')

NA

Create a Synapse file handle in memory which will hold a serialized version of one or more in-memory objects.  Additional parameters (...) are interpreted as properties or annotations, in the manner of synSet(), defined below. If 'synapseStore' is TRUE then file is uploaded to S3, else only the file location is saved.

The object is not serialized at this time. 

(We are hoping people will like calling the object a File, even though it's a collecton of in-memory objects.)

File(parentId)

 

example:

file<-File(parentId="syn101")

file<-addObject(file, obj)

 

Will not be implemented in python.

NA

Create a Folder or Project in memory. Name and parentId are optional.

 

Folder(name=NULL, parentId=NULL, ...)

Project(name=NULL, ...)

example:
Folder(name="foo", parentId="syn101")

Folder(name="foo", parentId="syn101", **kwargs)

Project(name="foo", **kwargs)

 

Set an entity's attribute (property or annotation) in memory.  Client first checks properties, then goes to annotations; (setting to NULL deletes it in R, using DEL operator in python deletes it)

TODO:  we want to include files and (for R) in memory objects

synAnnot(entity, name)<-value

entity.parentId="syn101"

synapse update id --parentId syn101

Gets an entity's attribute value (property or annotation) from the object already in memory.

 

synAnnot(entity, name); returns NULL if undefined

entity.name; throws exception if value is undefined

 

Create or update an entity (File, Folder, etc.) in Synapse.  May also specify (1) the list of entities 'used' to generate this one, (2) the list of entities 'executed' to generate this one, (3) the name of the generation activity, and (4) the description of the generation activity, (5) whether a name collision in an attempted 'create' should become an 'update', (6) whether to 'force' a new version to be created, and (7) whether the data is restricted (which will put a download 'lock' on the data and contact the Synapse Access and Compliance team for review.

TODO:  Give some examples.

synStore(entity, used=NULL, executed=NULL, activityName=NULL, activityDescription=NULL, createOrUpdate=T, forceVersion=T, isRestricted=F)

 

 

synStore(entity, activity=NULL, createOrUpdate=T, forceVersion=T, isRestricted=F)

synapse.store(entity, used, executed, activityName=None, activityDescription=None, createOrUpdate=True, forceVersion=True, isRestricted=False)

 

synapse.store(entity, activity, createOrUpdate=True, forceVersion=True, isRestricted=False)

synapse create --name NAME --parentid PARENTID --description DESCRIPTION

--type TYPE

--file PATH

--update=T/F

--forceVersion=T/F

 

--annotations={foo=bar, bar=foo}

Delete an object from Synapse.  In the case of entities, move to the trash can.

 

synDelete(id)

synDelete(object)

synapse.delete(synid), synapse.delete(entity), synapse.delete(wiki), synapse.delete(evaluation), synapse.delete(activity) ##TODO, synapse.delete(submission)

 

Get an entity (file, folder, etc.) from the Synapse server, with its attributes (properties, annotations) and, optionally, with its associated file(s).  ifcollision is one of "keep.both", "keep.local", or "overwrite.local", telling the system what to do if a different file is found at the given local file location.

'download' and 'load' are ignored for objects other than Files.  If a downloadLocation is not provided a default location is used.  Collisions with existing files are handled according to the 'ifcollision' parameter.  Note, 'downloadLocation' must be a directory.

synGet(id, version, downloadFile=T, downloadLocation=NULL, ifcollision="keep.both", load=F)

synapse.get(id, version, downloadFile=True, downloadLocation=None, ifcollision="keep.both")

synapse get ID -v NUMBER

Get the downloaded location of the file associated with a File object.

If synGet was called with download=FALSE, getFilePath() NULL.

getFileLocation(file)

getFileURL(file)

file.path

file.url

TODO

Open the web browser to the page for this entity.

 

onWeb(entityId) / onWeb(entity)

synapse.onweb(entityId) / synapse.onweb(entity)

synapse onweb id

log-in

If fields are omitted, then values are retrieved from the configuration file or from cached API keys.

synapseLogin(username = "", password = "", sessionToken = "", apiKey = "", rememberMe = False)

synapseLogin()

synapse.login(email=None, password=None, sessionToken=None, apiKey=None, rememberMe=False, silent=False)

synapse.login()

synapse login -u USER -p PASSWORD

log-out

localOnly=T delete any local copies of sessionToken or apiKey

localOnly=F: -> (1) if client has sessionToken, then call "DELETE /session"; (2) do the localOnly part

synapseLogout(localOnly=F)

synapse.logout(local=False, clearCache=False)

synapse logout

invalidate API key

invlidate API key

invalidateAPIKey()

invalidateAPIKey()

 

2 –Advanced functions

    

Execute query

TODO:  pagination, e.g. the function returns an iterator. Look at current implementation in R client.

synQuery(queryString)

synapse.query(queryString)

synapse query

Find the Entities having attached file(s) which have the given md5.

Returns an EntityHeader list.

synMD5Query(md5)

synapse.md5Query(md5)

NA

we talked about this, but is it needed?

 

synGetEntity()

  

we talked about this, but is it needed?

 

synStoreEntity()

  

Retrieve the wiki for an object (Entity or Evaluation)

 

synGetWiki(owner)

synGetWiki(owner, id)

synapse.getWiki(owner, subpageId)

Examples:

synapse.getWiki(entity)

synapse.getWiki(evalution, 2342)

 

Retrieve wiki headers of evaluation or entity

 

synGetWikiHeaders(owner)

Synapse.getWikiHeaders(owner)

where owner is an evaluation or entity

 

Wiki construction

 

WikiPage(owner, title, markdown, attachments)

WikiPage(owner, title, markdown, attachments, parentWikiId)

'attachments' is a list of local file paths

Wiki(owner, title, markdown, attachmentFileHandleIds, parentWikiId=None)

 
  

synStore(wiki)

synapse.store(Wiki)

 
  

synGetAnnotations()

synapse.getAnnotations(entity/entityId)

 
  

synSetAnnotations()

synapse.setAnntotations(entity/entityId, annotations)

 
  

synGetProperties()

NA

NA

Access properties, throwing exception if property is not defined.

 

synSetProperties()

NA

NA

  

synGetAnnotation()

  
  

synSetAnnotation()

  

Access property, throwing exception if property is not defined.

 

synGetProperty()

NA

NA

Access property, throwing exception if property is not defined. Setting to NULL deletes.

 

synSetProperty()

NA

NA

Create an Activity (provenance object) in memory.

 

Activity(name, description, used, executed)

Activity(name, description, used, exectuted)

NA

Set the list of entities/urls 'used' (not 'executed') by an Activity.

 

used(activity)<-refererenceList

activity$used<-refererenceList

  

Set the list of entities/urls 'executed' (not 'used') by an Activity.

 

executed(activity)<-refererenceList

activity$executed<-referenceList

  

Get the list of entities/urls 'used' (not 'executed') by an Activity.

 

used(activity)

activity$used

  

Get the list of entities/urls 'executed' (not 'used') by an Activity.

 

executed(activity)

activity$executed

  

Create or update the Activity in Synapse

 

synStore(activity)

synapse.store(Activity)

NA

Get the Activity which generated the given entity.

 

synGetActivity(entity) / synGetActivity(entityId)

synapse.getActivity(entity/entityId)

NA

Empty trash can

    

Restore from trash can

   
 Run code, capturing output, code and provenance relationship.
 

synapseExecute(executable, args, resultParentId, codeParentId, resultEntityProperties = NULL,  resultEntityName=NULL, replChar=".")

synapse.execute(executable, args, resultParentId, codeParentId, resultEntityProperties = None,  resultEntityName=None, replChar=".")

NA

Create evaluation object

 

Evaluation(name, description, status)

Evaluation(name, description, status, contentSource)

NA

Retrieve an Evaluation.

 

synGetEvaluation(evaluationId)

  

Submit for evaluation

teamName is used only when the Evaluation queue is part of a Challenge.  teamName is the (unique) name of a Synapse Team, registered for the Challenge.

submit(evaluation, entity, submissionName, teamName)

synapse.submit(evaluation, entity, name=None, teamName=None)

synapse submitEvaluation

Adds participant to evaluation, userId is optional

  

Synapse.addEvaluationParticipant(evaluation, userId=None):

 

Get the participants in an evaluation

 

synGetParticipants(evaluationId,limit,offset)

  

Returns an iterator of submissions

 

synGetSubmissions(evaluationId, myown=F, status, limit, offset)

Synapse.getSubmissions(evaluation, status=None):

 

Get specific submission

 

synGetSubmission(id, downloadFile=T, downloadLocation=NULL, ifcollision="keep.both", load=F)

Synapse.getSubmission(id, downloadFile=True, downloadLocation=None, ifcollision="keep.both"):

 

Get status of of submission

 

synGetSubmissionStatus(id)

synGetSubmissionStatus(submission)

Synapse.getSubmissionStatus(submission):

 

Get a user profile (own or other's)

When retrieving own profile, all fields are returned.  When retrieving other's profile, only public fields are returned.

synGetUserProfile()

synGetUserProfile(principalId)

  
3  Table functions    
3.1  Basic Table functions    
Create a Column definiition in memory.name and type are required.  default, values and maxSize are optional.TableColumn(name, type, default, values, maxSize)new table.Column(name, type, default, values, maxSize) 
Store a Column definition in Synapse. tableColumn<-synStore(tableColumn)synapse.store(tableColumn) 
Create a schema in memory

'column's are TableColumn objects or IDs.

TODO:  Can 'parentId' be any entity or just a project?  If the latter, change from 'parentId', to 'projectId'.

schema<-TableSchema(name, parentId, columns,  ...)

 

schema=new table.Schema(name, parentId, columns, **kwargs) 
TODO:  Add commands to add/remove columns from a table.    
Store the schema to Synapse. 

schema<-synStore(schema)

schema = synapse.store(schema)

 
Retrieve the schema. schema<-synGet(id)schema=synapse.get(id) 
Delete the table. 

synDelete(schema)

synDelete(id)

synapse.delete(schema)

synapse.delete(id)

 
Create a set of rows in memory.

values may be a data frame or a path to a CSV file. schema is a TableSchema or its ID.

Returns a Table object, suitable for upload to Synapse.

t<-Table(tableSchema, values)

 

t = table.values(schema, values)

 
Store table content in Synapse.

Stores Table in Synapse.

If 'retrieveData' is true then return a TableDataFrame, else return the number of uploaded rows.

If verbose=TRUE (the default), shows a progress bar.

rs<-synStore(t, retrieveData=FALSE, verbose=TRUE)rs = synapse.store(t, retrieveData=False, verbose=True) 
Delete rows from a table.table is a TableDataFrame.  The rows indicated by the row labels are deleted.synDeleteRows(table)synapse.deleteRows(table) 

Query a Table. 

Result is saved in a local file.  If loadResult is true, it is loaded into memory as well.

If "verbose" is TRUE then show progress.

downloadLocation is and optional specification of where the downloaded file should go.  If omitted the file will be written into the file cache.

User may specify pagination.

 

Note:  data frames returned have row labels of the form "<row>-<version>" e.g. "101-2".  These rows labels are required when submitting updates to Synapse.

queryResult<-synTableQuery(sqlString, loadResult=TRUE, verbose=TRUE, downloadLocation)rs = synapse.tableQuery(sqlString, loadResult=TRUE, verbose=TRUE, downloadLocation) 
3.2 Table convenience functions:    
Create table columns in memory from data frame. columns<-as.TableColumns(dataframe)columns = table.asColumns(pandasFrame) 
  

columns<-as.TableColumns(filePath)

columns = table.asColumns(filePath)

 
Download the file for a given cell (row, column) in a table.

For R client, 'table' can be an ID or a Table object. 

The parameters 'downloadLocation', 'ifcollision' and 'load' are defined as in 'synGet' and 'synGetSubmission'.

filePath<-synDownloadTableFile(table, rowIdAndVersion, columnName, downloadLocation=NULL, ifcollision="keep.both")

example:

filePath<-synDownloadTableFile("syn12345", "42_2", "genotype")

filePath=table.downloadFile(rowIdAndVersion, columnName, downloadLocation=None, ifcollision="keep.both") 

4 – Web API Level functions

    

Execute GET request

See details below.

synRestGET(uri, endpoint)

synapse.restGET(uri, endpoint=None)*

 

Execute POST request

See details below.

synRestPOST(uri, body, endpoint)

synapse.restPOST(uri, body, endpoint=None)*

 

Execute PUT request

See details below.

synRestPUT(uri, body, endpoint)

synapse.restPUT(uri, body, endpoint=None)*

 

Execute DELETE request

See details below.

synRestDELETE(uri, endpoint)

synapse.restDELETE(uri, endpoint=None)*

 

Get the current set of web service endpoints.

 

synGetEndpoints()

  

Set the web service endpoints.

If no arguments are passed, then reset to the default endpoints.

synSetEndpoints(repo, auth, file, portal)

synSetEndpoints()

  
     

*The endpoint defaults to repoEndpoint and it would be useful to be able to pass arbitrary named arguments that are just passed on to the underlying http library.  For python for example the stream and file parameters could be useful to pass along the the filehandle requests for get and put. 

...