2.9.1 Find your app inputs

Once you have copied the public app admin/sbg-public-data/rna-seq-alignment-star/5 into your project, username/api-testing, the app id in your current project is username/api-testing/newcopyofstar. Conversely, you can use another app you already have in your project for this Quickstart.

To draft a new task, you need to specify the following:

• The name of the task
• An optional description
• The app id of the workflow you are executing
• The inputs for your workflow. In this case, the CWL app accepts four parameters: number, min, max, and seed.

You can always check the App details on the visual interface for task input requirements. To find the required inputs with R, you need to get an App object first.

app <- a$app(id = "RFranklin/api-testing-2/newcopyofstar")
# get input matrix
app$input_matrix()
app$input_matrix(c("id", "label", "type"))
# get required node only
app$input_matrix(c("id", "label", "type"), required = TRUE)

Conversely, you can load the app from a CWL JSON and convert it into an R object first, as shown below.

f1 <- system.file("extdata/app", "flow_star.json", package = "sevenbridges")
app <- convert_app(f1)
# get input matrix
app$input_matrix()

##                                id                    label    type
## 1                    #sjdbGTFfile              sjdbGTFfile File...
## 2                          #fastq                    fastq File...
## 3               #genomeFastaFiles         genomeFastaFiles    File
## 4 #sjdbGTFtagExonParentTranscript      Exons' parents name  string
## 5       #sjdbGTFtagExonParentGene                Gene name  string
## 6          #winAnchorMultimapNmax         Max loci anchors     int
## 7             #winAnchorDistNbins Max bins between anchors     int
##   required fileTypes
## 1    FALSE      null
## 2     TRUE      null
## 3     TRUE      null
## 4    FALSE      null
## 5    FALSE      null
## 6    FALSE      null
## 7    FALSE      null

app$input_matrix(c("id", "label", "type"))

##                                id                    label    type
## 1                    #sjdbGTFfile              sjdbGTFfile File...
## 2                          #fastq                    fastq File...
## 3               #genomeFastaFiles         genomeFastaFiles    File
## 4 #sjdbGTFtagExonParentTranscript      Exons' parents name  string
## 5       #sjdbGTFtagExonParentGene                Gene name  string
## 6          #winAnchorMultimapNmax         Max loci anchors     int
## 7             #winAnchorDistNbins Max bins between anchors     int

app$input_matrix(c("id", "label", "type"), required = TRUE)

##                  id            label    type
## 2            #fastq            fastq File...
## 3 #genomeFastaFiles genomeFastaFiles    File

Note that input_matrix and output_matrix are useful accessors for Tool, Flow, you can call these two function on a JSON file directly as well.

tool.in <- system.file("extdata/app", "tool_unpack_fastq.json", package = "sevenbridges")
flow.in <- system.file("extdata/app", "flow_star.json", package = "sevenbridges")
input_matrix(tool.in)
input_matrix(tool.in, required = TRUE)
input_matrix(flow.in)
input_matrix(flow.in, c("id", "type"))
input_matrix(flow.in, required = TRUE)
output_matrix(tool.in)
output_matrix(flow.in)

In the response body, locate the names of the required inputs. Note that task inputs need to match the expected data type and name. In the above example, we see two required fields:

• fastq: This input takes a file array as indicated by “File…”
• genomeFastaFiles: This is a single file as indicated by “File”.

We also want to provide a gene feature file:

• sjdbGTFfile: A single file as indicated by “File”.

You can find a list of possible input types below:

• number, character or integer: you can directly pass these to the input parameter as it is.
• enum type: Pass this value to the input parameter.
• file: This input is a file. However, while some inputs accept only single file (File), other inputs take more than one file (File arrays, FilesList, or ‘File...’ ). This input requires you to pass a Files object (for a single file input) or FilesList object (for inputs which accept more than one file) or simply a list in a “Files” object. You can search for your file by id or by name with an exact match (exact = TRUE), as shown in the example below.

2.9.2 Get your input files ready

fastqs <- c("SRR1039508_1.fastq", "SRR1039508_2.fastq")

# get all 2 exact files
fastq_in <- p$file(name = fastqs, exact = TRUE)

# get a single file
fasta_in <- p$file(
  name = "Homo_sapiens.GRCh38.dna.primary_assembly.fa",
  exact = TRUE
)
# get all single file
gtf_in <- p$file(
  name = "Homo_sapiens.GRCh38.84.gtf",
  exact = TRUE
)

2.9.3 Create a new draft task

# add new tasks
taskName <- paste0("RFranklin-star-alignment ", date())

tsk <- p$task_add(
  name = taskName,
  description = "star test",
  app = "RFranklin/api-testing-2/newcopyofstar/0",
  inputs = list(
    sjdbGTFfile = gtf_in,
    fastq = fastq_in,
    genomeFastaFiles = fasta_in
  )
)

Remember the fastq input expects a list of files. You can also do something as follows:

f1 <- p$file(name = "SRR1039508_1.fastq", exact = TRUE)
f2 <- p$file(name = "SRR1039508_2.fastq", exact = TRUE)
# get all 2 exact files
fastq_in <- list(f1, f2)

# or if you know you only have 2 files whose names match SRR924146*.fastq
fastq_in <- p$file(name = "SRR1039508*.fastq", complete = TRUE)

Use complete = TRUE when the number of items is over 100.

2.9.4 Draft a batch task

Now let’s do a batch with 8 files in 4 groups, which is batched by metadata sample_id and library_id. We will assume each file has these two metadata fields entered. Since these files can be evenly grouped into 4, we will have a single parent batch task with 4 child tasks.

fastqs <- c(
  "SRR1039508_1.fastq", "SRR1039508_2.fastq", "SRR1039509_1.fastq",
  "SRR1039509_2.fastq", "SRR1039512_1.fastq", "SRR1039512_2.fastq",
  "SRR1039513_1.fastq", "SRR1039513_2.fastq"
)

# get all 8 files
fastq_in <- p$file(name = fastqs, exact = TRUE)
# can also try to returned all SRR*.fastq files
# fastq_in <- p$file(name= "SRR*.fastq", complete = TRUE)

tsk <- p$task_add(
  name = taskName,
  description = "Batch Star Test",
  app = "RFranklin/api-testing-2/newcopyofstar/0",
  batch = batch(
    input = "fastq",
    criteria = c("metadata.sample_id", "metadata.noexist_id")
  ),
  inputs = list(
    sjdbGTFfile = gtf_in,
    fastq = fastqs_in,
    genomeFastaFiles = fasta_in
  )
)

Now you have a draft batch task. Please check it out in the visual interface. Your response body should inform you of any errors or warnings.

Note: you can also directly pass file id or file names as characters to inputs list, the package will first guess if the passed strings are file id (24-bit hexadecimal) or names, then convert it to Files or FilesList object. However, as a good practice, we recommend you construct your files object(e.g. p$file(id = ..., name = ...)) first, check the value, then pass it to task_add inputs. This is a safer approach.

3.1.1 Direct authentication

To use direct authentication, users need to specify one of platform or url, with the corresponding token. Examples of direct authentication:

a <- Auth(
  token = "your_token",
  platform = "aws-us"
)

The above will use the Seven Bridges Platform on AWS (US).

a <- Auth(
  token = "your_token",
  url = "https://gcp-api.sbgenomics.com/v2"
)

The above will use the specified url as the base URL for the API calls. In this example, the url points to the Seven Bridges Platform on Google Cloud Platform (GCP).

a <- Auth(token = "your_token")

The above will use the Cancer Genomics Cloud environment since no platform nor url were explicitly specified (not recommended).

Note: platform and url should not be specified at the same time.

3.1.2 Authentication via system environment variables

The R API client supports reading authentication information stored in system environment variables.

To set the two environment variables in your system, you could use the function sbg_set_env(). For example:

sbg_set_env(
  url = "https://cgc-api.sbgenomics.com/v2",
  token = "your_token"
)

See if the environment variables are correctly set:

sbg_get_env("SB_API_ENDPOINT")
## "https://cgc-api.sbgenomics.com/v2"
sbg_get_env("SB_AUTH_TOKEN")
## "your_token"

To create an Auth object:

a <- Auth(from = "env")

To unset the two environment variables:

Sys.unsetenv("SB_API_ENDPOINT")
Sys.unsetenv("SB_AUTH_TOKEN")

3.1.3 Authentication via user configuration file

You can create an ini-like file named credentials under the folder $HOME/.sevenbridges/ and maintain your credentials for multiple accounts across various Seven Bridges environments. An example:

[aws-us-rfranklin]
api_endpoint = https://api.sbgenomics.com/v2
auth_token = token_for_this_user

# This is a comment:
# another user on the same platform
[aws-us-rosalind-franklin]
api_endpoint = https://api.sbgenomics.com/v2
auth_token = token_for_this_user

[default]
api_endpoint = https://cgc-api.sbgenomics.com/v2
auth_token = token_for_this_user

[gcp]
api_endpoint = https://gcp-api.sbgenomics.com/v2
auth_token = token_for_this_user

Please make sure to have two fields exactly named as api_endpoint and auth_token under each profile.

To load the default profile (named [default]) from the default user configuration file ($HOME/.sevenbridges/credentials), please use:

a <- Auth(from = "file")

To load the user profile aws-us-rfranklin from this configuration file, change the profile_name:

a <- Auth(from = "file", profile_name = "aws-us-rfranklin")

To use a user configuration file from other locations (not recommended), please specify the file path using the argument config_file. For example:

a <- Auth(
  from = "file", config_file = "~/sevenbridges.cfg",
  profile_name = "aws-us-rfranklin"
)

Note: If you edited the credentials file, please use Auth() to re-authenticate.

3.3.1 offset and limit

Every API call accepts two arguments named offset and limit.

• offset defines where the retrieved items started.
• limit defines the number of items you want to get.

By default, offset is set to 0 and limit is set to 50. As such, your API request returns the first 100 items when you list items or search for items by name. To search and list all items, use complete = TRUE in your API request.

getOption("sevenbridges")$offset
getOption("sevenbridges")$limit

3.3.2 Search by ID

When searching by ID, your request will return your exact resource as it is unique. As such, you do not have to set offset and limit manually. It is a good practice to find your resources by their ID and pass this ID as an input to your task. You can find a resource’s ID in the final part of the URL on the visual interface or via the API requests to list resources or get a resource’s details.

3.3.3 Search by name

Search by name returns all partial matches unless you specify exact = TRUE. This type of search will only search across current pulled content, so use complete = TRUE if you want to search across everything.

For example, to list all public apps, use visibility argument, but make sure you pass complete = TRUE to it, to show everything. This arguments generally works for items like “App”, “Project”, “Task”, “File”, etc.

# first, search by id is fast
x <- a$app(visibility = "public", id = "admin/sbg-public-data/sbg-ucsc-b37-bed-converter/1")

# show 100 items from public
x <- a$app(visibility = "public")
length(x) # 100

x <- a$app(visibility = "public", complete = TRUE)
length(x) # 272 by Nov 2016
# this return nothing, because it is not in the first 100 returned names
a$app(visibility = "public", name = "bed converter")
# this return an app, because it pulls *all* app names and did search
a$app(visibility = "public", name = "bed converter", complete = TRUE)

3.3.4 Experiment with Advance Access features

Similar to offset and limit, every API call accepts an argument named advance_access. This argument was first introduced in August 2017 and controls if a special field in the HTTP request header will be sent, which can enable the access to the “Advance Access” features in the Seven Bridges API. Note that the Advance Access features in the API are not officially released yet, therefore the API usages are subject to change, so please use with discretion.

In addition to modifying each API call that uses Advance Access features, the option can also be set globally at the beginning of your API script. This offers a one-button switch for users who want to experiment with the Advance Access features. The option is disabled by default:

library("sevenbridges")
getOption("sevenbridges")$advance_access

## [1] FALSE

For example, the Markers API is in Advance Access as of November 2018. If we try to use the Markers API to list markers available on a BAM file with the advance_access option disabled, it will return an error message:

req <- api(
  token = "your_token", path = "genome/markers?file={bam_file_id}",
  method = "GET"
)

httr::content(req)$"message"

## [1] "Advance access feature needs X-SBG-Advance-Access: advance header."

To enable the Advance Access features, one can use

opt <- getOption("sevenbridges")
opt$advance_access <- TRUE
options(sevenbridges = opt)

at the beginning of their scripts. Let’s check if the option has been enabled:

getOption("sevenbridges")$advance_access

## [1] TRUE

Send the API call again:

req <- api(
  token = "your_token", path = "genome/markers?file={bam_file_id}",
  method = "GET"
)

The information of the markers available on that BAM file will be returned:

httr::content(req)

$href
[1] "https://api.sbgenomics.com/v2/genome/markers?file={bam_file_id}&offset=0&limit=2"

$items
$items[[1]]
$items[[1]]$href
[1] "https://api.sbgenomics.com/v2/genome/markers/{bam_file_id}"

$items[[1]]$id
[1] "{bam_file_id}"

$items[[1]]$name
[1] "Marker Title"

$items[[2]]
$items[[2]]$href
[1] "https://api.sbgenomics.com/v2/genome/markers/{bam_file_id}"

$items[[2]]$id
[1] "{bam_file_id}"

$items[[2]]$name
[1] "Marker Title"

$links
list()

3.7.1 For billing

If no billing group id is provided, this call returns a list of paths used to access billing information via the API. If a username is provided, this call lists all your billing groups, including groups that are pending or which have been disabled. If you specify breakdown = TRUE, the call below returns a breakdown of the spending per-project for the billing group specified by billing_group. Information is also displayed for each of the projects a particular billing group is associated with, including task executions, their initiating user, start and end time, and their cost.

# return a BillingList object
(b <- a$billing())
a$billing(id = b$id, breakdown = TRUE)

3.7.2 For invoices

If no Billing Group id provided, This call returns a list of invoices, with information about each, including whether or not the invoice is pending and the billing period it covers. This call returns information about all your available invoices unless you use the query parameter bg_id to specify the ID of a particular Billing Group, in which case it will return the invoice incurred by that Billing Group only. If an invoice id is provided, this call retrieves information about the specified invoice, including the costs for analysis and storage and the invoice period.

a$invoice()
a$invoice(id = "your_id")

Note: Currently, invoice is not an object. Instead, it just returns a regular R list.

3.8.1 List all projects

The following call returns a list of all projects of which you are a member. Each project’s project_id and the path will be returned.

a$project()

If you want to list the projects owned by and accessible to a particular user, specify the owner argument as follows. Each project’s ID and path will be returned.

a$project(owner = "RFranklin")
a$project(owner = "Rosalind.Franklin")

To get details about the project(s), use detail = TRUE, as shown below.

a$project(detail = TRUE)

3.8.2 Partial match project name

For a more friendly interface and convenient search, the sevenbridges package supports partial name matching. The first argument for the following request is name.

# want to return a project called
a$project("hello")

3.8.3 Filter by project creation date, modification date, and creator

Project creation date, modification date, and creator information is useful for quickly locating the project you need, especially when you want to follow the life cycle of a large number of projects and distinguish recent projects from old ones. To facilitate such needs, the fields created_by, created_on, and modified_on are returned in the project query calls:

# return all projects matching the name "wgs"
p <- a$project("wgs", complete = TRUE)

# filter by project creators
creators <- sapply(p, "[[", "created_by")
which(creator == "RFranklin")

# filter by project creation date
create_date <- as.Date(sapply(p, "[[", "created_on"))
which(as.Date(create_date) < as.Date("2019-01-01"))

# filter by project modification date
modify_date <- as.Date(sapply(p, "[[", "modified_on"))
which(as.Date(modify_date) < as.Date("2019-01-01"))

3.8.4 Create a new project

To create a new project, users need to specify the following:

• name (required)
• billing_group_id (required)
• description (optional)
• tags (optional): This has to be a list(). If you are using the API on the CGC environment, you can create a TCGA Controlled Data project by specifying TCGA in tags.
• type (optional): By default, we create a V2, CWL compatible project.

a$project_new("api_testing_tcga", b$id,
  description = "Test for API"
)

3.8.5 Create a new project with TCGA controlled data on CGC

Follow the directions above, but pass tcga as a value for tags.

a$project_new("controlled_project", b$id,
  description = "Test for API", tags = list("tcga")
)

3.8.6 Delete a project

You can delete a single project by making the request to $delete(). Note that the returned object from a$project() sometimes returns list if you use partial matching by name. The $delete() request cannot operate on a list. If you want to operate on a list of object, read more about batch functions in the relevant section below.

# remove it, not run
a$project("api_testing")$delete()
# check
# will delete all projects match the name
delete(a$project("api_testing_donnot_delete_me"))

3.8.7 Update/edit a project

You can update the following information about an existing project:

• name
• description
• billing_group_id

a$project(id = "RFranklin/helloworld")
a$project(id = "RFranklin/helloworld")$update(
  name = "Hello World Update",
  description = "Update description"
)

3.8.8 Project member

a$project(id = "RFranklin/demo-project")$member()

m <- a$project(id = "RFranklin/demo-project")$
  member_add(username = "Rosalind.Franklin")

m <- a$project(id = "RFranklin/demo-project")$
  member(username = "Rosalind.Franklin")
m$update(copy = TRUE)

== Member ==
username : Rosalind.Franklin
-- Permission --
read : TRUE
write : FALSE
copy_permission : TRUE
execute : FALSE
admin : FALSE

m$delete()
# confirm
a$project(id = "RFranklin/demo-project")$member()

3.8.9 List all files

To list all files belonging to a project, use the following request:

p <- a$project(id = "RFranklin/demo-project")
p$file()

3.9.1 List all files

A better way to list files in a project uses the following:

# first 100 files, default offset = 0, limit = 100
p$file()
# list all files
p$file(complete = TRUE)

Alternatively, you can get files from the Auth object.

a$file(project = p$id)
a$file(name = "omni", project = p$id, detail = TRUE)

3.9.2 Search and filter file(s)

p <- a$project(id = "RFranklin/demo")
p$file(
  metadata = list(
    sample_id = "Sample1",
    sample_id = "Sample2",
    library_id = "EXAMPLE"
  ),
  tag = c("hello", "world")
)

# return single object id is "some_file_id"
p$file(id = "some_file_id")
# return a single object named a.fastq
p$file(name = "a.fastq", exact = TRUE)
# public file search using Auth object
a$public_file(name = "ucsc.hg19.fasta.fai", exact = TRUE)
a$public_file(id = "578cf94a507c17681a3117e8")

# get two files
p$file(name = c("test1.fastq", "test2.fastq"), exact = TRUE)
# get two files from public files using shorthand
a$public_file(
  name = c("ucsc.hg19.fasta.fai", "ucsc.hg19.fasta"),
  exact = TRUE
)

# get matchd the pattern for searching first 100 files
p$file(name = c("gz", "fastq"))
# get all matched files from the project
p$file(name = c("gz", "fastq"), complete = TRUE)
# get all files matched ucsc
a$public_file(name = "ucsc.hg19", complete = TRUE)

p <- a$project(id = "RFranklin/demo")
p$file(metadata = list(
  sample_id = "Sample1",
  sample_id = "Sample2",
  library_id = "EXAMPLE"
))

p <- a$project(id = "RFranklin/demo")
p$file(tag = c("s1", "s2"))

# list all outputs file from a task id
a$task(id = "53020538-6936-422f-80de-02fa65ae4b39")$file()

# OR
p <- a$project(id = "RFranklin/demo")
p$file(origin.task = "53020538-6936-422f-80de-02fa65ae4b39")

3.9.3 Copy a file or group of files

This call copies the specified file to a new project. Files retain their metadata when copied, but may be assigned new names in their target project.

Note that Controlled Data files may not be copied to Open Data projects. To make this request, you should have copy permission within the project you are copying from.

Let’s try to copy a file from the Public File repository. The file’s id is “561e1b33e4b0aa6ec48167d7”.

You must provide

• id: file id or list/vector of files ids
• project: project id.
• name (optional):if omitted, use the same name as the original file name

# 1000G_omni2.5.b37.vcf
fid <- "561e1b33e4b0aa6ec48167d7"
fid2 <- "561e1b33e4b0aa6ec48167d3"
pid <- a$project("demo")$id
a$copyFile(c(fid, fid2), project = pid)
a$project(id = pid)$file()

NOTE: To copy a group of files, you need the Auth$copyFile() interface. The id of the files in your project will be different from their id in the Public Files repository.

Alternatively, you copy a single file as shown below.

a$project("hello")$file(id = fid)$copyTo(pid)

Notably, if you have many files to copy between projects, we would always recommend using the Auth$bulk_file_copy() method described in the Actions API section below, to batch copy the files in a single API call and save the number of API calls.

3.9.4 Delete file(s)

Note: The delete action only works for one file at a time. Be sure your file call returns a single file rather than a file list.

a$project("demo")$file()[[1]]$delete()
## confirm the deletion
a$project("demo")$file()

You can also delete a group of files or FilesList object, just be careful when using this function.

## return 5 files
a$project("demo")$file("phase1")
## delete all of them
delete(a$project("demo")$file("phase1"))
a$project("demo")$file("phase1")

3.9.5 Download files

To get the download information, please use the following:

a$project("demo")$file()[[1]]$download_url()

To download directly from R, use the download call directly from a single File object.

fid <- a$project("demo")$file()[[1]]$id
a$project("demo")$file(id = fid3)$download("~/Downloads/")

I also created a download function for FilesList object to save your time, as follows:

fls <- a$project("demo")$file()
download(fls, "~/Downloads/")

To download all files from a project, use the following:

a$project("demo")$download("~/Downloads")

3.9.6 Upload files via API

Seven Bridges platforms provide a few different methods for data import:

• Import from FTP or HTTP with the web interface
• The GUI uploader
• The file upload API that you can directly call with the sevenbridges package
• The command line uploader which can be invoked with the sevenbridges package

Use the API client uploader by calling the project$upload function to upload a file, a file list, or a folder recursively or via a manifest file.

a <- Auth(username = "RFranklin", platform = "cgc")
fl <- system.file("extdata", "sample1.fastq", package = "sevenbridges")

(p <- a$project(id = "RFranklin/quickstart"))

# by default load .meta for the file
p$upload(fl, overwrite = TRUE)
# pass metadata
p$upload(fl, overwrite = TRUE, metadata = list(library_id = "testid2", platform = "Illumina x11"))
# rename
p$upload(fl,
  overwrite = TRUE, name = "sample_new_name.fastq",
  metadata = list(library_id = "new_id")
)

dir.ext <- system.file("extdata", package = "sevenbridges")
list.files(dir.ext)
p$upload(dir.ext, overwrite = TRUE)

dir.ext <- system.file("extdata", package = "sevenbridges")
# enable full name
fls <- list.files(dir.ext, recursive = TRUE, full.names = TRUE)
p$upload(fls, overwrite = TRUE)
p$upload("~/Documents/Data/sbgtest/1000G_phase1.snps.high_confidence.b37.vcf")

# upload all fiels and all metadata
p$upload(manifest_file = "~/manifest.csv")

# verbal = TRUE, print single file level progress
p$upload(manifest_file = "~/manifest.csv", overwrite = TRUE, verbal = TRUE)

# manifest_metadata = FALSE doens't attach any metadata
p$upload(manifest_file = "~/manifest.csv", manifest_metadata = FALSE, overwrite = TRUE)

# filter files first, upload only files with score < 0.5
p$upload(manifest_file = "~/manifest.csv", overwrite = TRUE, subset = score < 0.5)

# attach all meta except "bad_field" and "sample_id"
p$upload(
  manifest_file = "~/manifest.csv", overwrite = TRUE,
  subset = score < 0.5, select = -c(bad_field, sample_id)
)

3.9.7 Upload files via command line uploader

As an alternative to API file uploading, we also offer an interface in the sevenbridges package for uploading (possibly large) files via the Java-based command line uploader.

The first step is to download the command line uploader. With get_uploader(), users can easily download the uploader to a local directory for a specified Seven Bridges platform, for example, the Cancer Genomics Cloud:

get_uploader("cgc", "~/Downloads/")

To list the available projects accessible from your account via the uploader, use cli_list_projects(), with your authentication token for that platform and the directory containing the uploader:

cgc_token <- "your_cgc_token"
cgc_uploader <- "~/Downloads/cgc-uploader/"

cli_list_projects(
  token = cgc_token,
  uploader = cgc_uploader
)

The function will return a character vector containing the available projects which you could upload files to, in the form of username/project-name.

Similarly, to list all the file tags in a project via the uploader, use cli_list_tags():

cli_list_tags(
  token = cgc_token,
  uploader = cgc_uploader,
  project = "username/project-name"
)

Eventually, use cli_upload() to upload local files to a project:

cli_upload(
  token = cgc_token,
  uploader = cgc_uploader,
  file = "~/example.fastq",
  project = "username/project-name"
)

3.9.8 Update a file

You can call the update() function from the Files object. With this call, the following can be updated:

• The file’s name.
• The file’s metadata. The metadata is in the form of a list. Note that as this call overwrites all the metadata for a given file, please supply a full list of all the metadata for the file. Conversely, you can use the set_meta() function to patch but not overwrite the metadata for a file.

If no parameters were provided, this call will get the details of that file and update the object itself.

(fl <- a$project(id = "RFranklin/demo-project")$file(name = "sample.fastq"))

== File ==
id : 56c7916ae4b03b56a7d7
name : sample.fastq
project : RFranklin/demo-project

Show metadata

# show metadata
fl$meta()

Update meta

fl$update(
  name = "sample.fastq",
  metadata = list(
    new_item1 = "item1",
    new_item2 = "item2",
    file_extension = "fastq"
  )
)
# check it out
fl$meta()

3.9.9 Metadata operations

Learn about metadata fields and their values for the relevant environment: [Seven Bridges Platform] [CGC].

Note that the name of a file is not the same as its ID. A file’s ID is a hexadecimal string automatically assigned to a file in a project. The file’s name is a human-readable string. For information, please see the API overview for the Seven Bridges Platform and for the CGC.

Get metadata

To get the metadata for a file, call the meta() function, as shown below.

# meta is pulling the latest information via API
fl$meta()
# field metadata saved the previously saved one
fl$metadata

Set metadata

Files from curated datasets on Seven Bridges environments have a defined set of metadata which is visible on the visual interface of each environment. However, you can also pass additional metadata for each file which is stored with your copy of the file in your project.

To set metadata but not overwrite all previously stored metadata, call the set_meta() function from the Files object. Unlike the update() function for the Files object, the set_meta() function doesn’t overwrite the metadata field. To overwrite the metadata field, use the update() function or pass the optional argument overwrite = TRUE for the set_meta() call.

fl$set_meta(new_item3 = "item3")
fl
# oops it removed rest of the meta
fl$set_meta(new_item4 = "item4", overwrite = TRUE)
fl

Check details of each metadata field

You can use the Metadata() constructor to check the details of each metadata field. Simply call the function (name of the metadata) to display descriptions and enumerated items. Please pay attention to the suggested_values field.

# check which schema we have
Metadata()$show(full = TRUE)
# check details for each, play with it
platform()
paired_end()
quality_scale()

As you can see, some metadata fields have suggested values. To construct the metadata, use Metadata() directly to pass the metadata fields and their values directly into the call. The call will perform the validation.

Metadata(
  platform = "Affymetrix SNP Array 6.0",
  paired_end = 1,
  quality_scale = "sanger",
  new_item = "new test"
)

3.9.10 Tag file(s)

You can tag your files with keywords or strings to make it easier to identify and organize files. Tags are different from metadata and are more convenient and visible from the files list on the visual interface.

Add a new tag

To add a new tag, call the obj$add_tag() method for the File object with a single tag string or a list or vector of tags.

Overwrite the tags for a file

To completely overwrite the tags for a file, use the obj$set_tag() method, which contains the default argument overwrite = TRUE.

Let’s use a file called sample.bam and play with its tags.

p <- a$project(id = "RFranklin/s3tutorial")
fl <- p$file("sample.bam", exact = TRUE)
# show tags for single file
fl$tag()
# add new tags
fl$add_tag("new tag")
# equavilent to
fl$set_tag("new tag 2", overwrite = FALSE)
# set tags to overwrite existing
x <- list("this", "is", 1234)
fl$set_tag(x)
# filter by tags
p$file(tag = c("1234", "new"))
p$file(tag = list("1234", "new"))
p$file(tag = "1234")

Below, find convenient methods for FilesList. Let’s add the tag “s1” to a group files matching “Sample1” and add the tag “s2” to a group of files that match “s2”. Then, we will filter by these tags to obtain specific files.

# work on a group of files
# add tag "s2" to a group of files named with "Sample2" in it
fl2 <- p$file("Sample2")
add_tag(fl2, "s2")
# add tag "s2" to a group of files named with "Sample1" in it
fl1 <- p$file("Sample1")
add_tag(fl1, "s1")
# filter by tag s1 or s2
p$file(tag = "s1")
p$file(tag = "s2")
# get files tagged with s2 and 1234
p$file(tag = list("s2", "s1"))

3.10.1 Get project root folder

To create new folders and manage files using folders in a project, we first need to get the information about the root folder of the project. For example

p <- a$project(id = "RFranklin/folders-api-testing")

We can get the project root folder ID:

p$get_root_folder_id()

[1] "5bd7c53ee4b04b8fb1a9f63c"

Or, return the project root folder as an object:

(root_folder <- p$get_root_folder())

== Files ==
id : 5bd7c53ee4b04b8fb1a9f63c
name : 8c02ceda-e46b-49c0-362f-4318fa8f3e4k
project : RFranklin/folders-api-testing
created_on : 2018-10-29T18:45:50Z
modified_on : 2018-10-29T18:45:50Z
type : folder

3.10.2 Create a folder

To create a new_folder under the project root folder, use

folder1 <- root_folder$create_folder("folder1")

To create a new folder under folder1, use

folder2 <- folder1$create_folder("folder2")

3.10.3 Copy files between folders

Let’s copy a public reference file into the project root folder:

file_public <- a$public_file(name = "Homo_sapiens_assembly38.fasta", exact = TRUE)
file1 <- file_public$copy_to_folder(root_folder$id)

We can also rename the file when copying it into a folder:

file2 <- file_public$copy_to_folder(root_folder$id, "ref_grch38.fasta")

3.10.4 Move files between folders

To move files to another folder (for example, folder1 we just created), use

file1 <- file1$move_to_folder(folder1$id)

3.10.5 List folder contents

To list all files and folders in a folder (for example, the root folder), use

(contents_root <- root_folder$list_folder_contents(complete = TRUE))

[[1]]
== Files ==
id : 5bede476e4b03b8ff38c28ba
name : folder1
project : RFranklin/folders-api-testing
parent : 5bd7c53ee4b04b8fb1a9f63c
type : folder

[[2]]
== Files ==
id : 5bedc431e4b09b8ff3966e9c
name : ref_grch38.fasta
project : RFranklin/folders-api-testing
parent : 5bd7c53ee4b04b8fb1a9f63c
type : file

If complete = FALSE (default), it will only return the (first) page from the API based on offset and limit.

To list only files or only folders, set type = "file" or type = "folder":

root_folder$list_folder_contents(type = "file", complete = TRUE)
root_folder$list_folder_contents(type = "folder", complete = TRUE)

3.10.6 Get file and folder details

Get the type of a single file/folder object:

contents_root[[1]]$typeof()

[1] "folder"

Or, get the type(s) for all objects in the folder:

sapply(contents_root, function(x) x$typeof())

[1] "folder" "file"

Sometimes, it’s convenient to get the parent folder ID for a file or folder:

contents_root[[1]]$get_parent_folder_id()

[1] "5bd7c53ee4b04b8fb1a9f63c"

This is essentially the root folder ID. Alternatively, to get the parent folder as an object, use

contents_root[[1]]$get_parent_folder()

3.10.7 Delete files in a folder

We can delete a file in a folder:

file1$delete()

3.10.8 Delete a folder

If a folder still has files in it, it cannot be deleted:

file2 <- file2$move_to_folder(folder2$id)
folder2$delete()

Error: HTTP Status 400: Deleting non-empty folders is not supported.

We need to delete all files (and subfolders) within a folder before deleting the folder itself:

file2$delete()
folder2$delete()
folder1$delete()

3.11.1 List all apps

This call lists all the apps available to you.

a$app()
# or show details
a$app(detail = TRUE)

Search for an app by name

To search for a specific app by its name, pass a pattern for the name argument or provide a unique id as shown below.

# pattern match
a$app(name = "STAR")
# unique id
aid <- a$app()[[1]]$id
aid
a$app(id = aid)
# get a specific revision from an app
a$app(id = aid, revision = 0)

List all apps in a project

To list all apps belonging to a specific project, use the project argument.

# my favorite, always
a$project("demo")$app()

# or alternatviely
pid <- a$project("demo")$id
a$app(project = pid)

List all public apps

To list all public apps, use the visibility argument.

# show 100 items from public
x <- a$app(visibility = "public")
length(x)
x <- a$app(visibility = "public", complete = TRUE)
length(x)
x <- a$app(project = "RFranklin/helloworld", complete = TRUE)
length(x)
a$app(visibility = "public", limit = 5, offset = 150)

Search through all public apps in all locations

To search for a public app cross all locations, make the following call. Note that this may take a bit of time.

a$app("STAR", visibility = "public", complete = TRUE)

3.11.2 Copy an app

This call copies the specified app to a specified project. The app should be one in a project that you can access, either an app which has been uploaded by a project member or a publicly available app which has been copied to the project.

This call requires the following two arguments:

• project: include the project id
• name (optional): use this field to optionally re-name your app

aid <- a$public_app()[[1]]$id
a$copy_app(aid, project = pid, name = "copy-rename-test")
# check if it is copied
a$app(project = pid)

You can also copy directly from the app object, as shown below.

app <- a$public_app(id = "admin/sbg-public-data/rna-seq-alignment-star")
app$copy_to(
  project = "RFranklin/api-testing",
  name = "copy of star"
)

3.11.3 Get an app’s CWL description

This call returns the raw CWL of a specific app, including its raw CWL. The call differs from the call to GET details of an app in that it returns a JSON object that is the CWL.

The app should be one in a project that you can access, either an app which has been uploaded by a project member or a publicly available app which has been copied to the project.

To get a specific revision, pass the revision argument.

ap <- a$app(visibility = "public")[[1]]
a$project("demo")$app("index")
# get a specific revision
a$project("demo")$app("index", revision = 0)

Coming soon: converting apps to CWL objects

3.11.4 Add CWL as an app

To add a CWL object as an app, use the app_add function call for a Project object. The following two parameters are required:

• short_name: Project short names are based on the name you give to a project when you create it. Learn more about project short names on the Seven Bridges Platform or the CGC.
• filename: The name of the JSON file containing the CWL.

cwl.fl <- system.file("extdata", "bam_index.json", package = "sevenbridges")
a$project("demo")$app_add(short_name = "new_bam_index_app", filename = cwl.fl)
a$project("demo")$app_add(short_name = "new_bam_index_app", revision = 2, filename = cwl.fl)

Note: If you provide the same short_name, this will add a new revision.

3.11.5 Describe CWL in R directly

This is introduced in another vignette (vignette("apps", "sevenbridges")).

3.11.6 Create test or keep the previous test for Tool

On Seven Bridges platforms, when you create or update your tools in the GUI, there is a test tab allow users to tweak the parameters and see what it looks like in your command line simulated terminal. To do this via R when you push your Tool object to your project, you need to provide "sbg:job" information like the example shown below

rbx <- Tool(
  id = "runif",
  label = "Random number generator",
  hints = requirements(
    docker(pull = "RFranklin/runif"),
    cpu(1), mem(2000)
  ),
  baseCommand = "runif.R",
  inputs = in.lst,
  outputs = out.lst,
  "sbg:job" = list(
    allocatedResources = list(mem = 9000, cpu = 1),
    inputs = list(min = 1, max = 150)
  )
)
p$app_add("random", rbx)

Or if you have created test info on the platform or previously pushed one, and you want to keep the previous test setup. We provide an argument named keep_test to allow you to keep the previous revision’s test information.

rbx <- Tool(
  id = "runif",
  label = "Random number generator",
  hints = requirements(
    docker(pull = "RFranklin/runif"),
    cpu(1), mem(2000)
  ),
  baseCommand = "runif.R",
  inputs = in.lst,
  outputs = out.lst
)
p$app_add("random", rbx, keep_test = TRUE)

3.12.1 List tasks

This call returns a list of tasks that you can access. You can filter tasks by status.

# all tasks
a$task()
# filter
a$task(status = "completed")
a$task(status = "running")

To list all the tasks in a project, use the following.

# a better way
a$project("demo")$task()

# alternatively
pid <- a$project("demo")$id
a$task(project = pid)

To list all tasks with details, pass detail = TRUE.

p$task(id = "your task id here", detail = TRUE)
p$task(detail = TRUE)

To list a batch task using the parent parameter, pass the batch parent task id.

p <- a$project(id = "RFranklin/demo")
p$task(id = "2e1ebed1-c53e-4373-870d-4732acacbbbb")
p$task(parent = "2e1ebed1-c53e-4373-870d-4732acacbbbb")
p$task(parent = "2e1ebed1-c53e-4373-870d-4732acacbbbb", status = "completed")
p$task(parent = "2e1ebed1-c53e-4373-870d-4732acacbbbb", status = "draft")

3.12.2 Create a draft task

To create a draft task, you need to call the task_add function from the Project object. And you need to pass the following arguments:

• name: The name for this task
• description (optional): A description for this task
• app: The app id
• inputs: A list of inputs for this task

# push an app first
fl.runif <- system.file("extdata", "runif.json", package = "sevenbridges")
a$project("demo")$app_add("runif_draft", fl.runif)
runif_id <- "RFranklin/demo-project/runif_draft"
# create a draft task
a$project("demo")$task_add(
  name = "Draft runif 3",
  description = "Description for runif 3",
  app = runif_id,
  inputs = list(min = 1, max = 10)
)
# confirm
a$project("demo")$task(status = "draft")

3.12.3 Modify a task

Call the update function from a Task object to update the following:

• name
• description
• inputs list. Note that you can only update the items you provided.

# get the single task you want to update
tsk <- a$project("demo")$task("Draft runif 3")
tsk
tsk$update(
  name = "Draft runif update",
  description = "draft 2",
  inputs = list(max = 100)
)
# alternative way to check all inputs
tsk$getInputs()

3.12.4 Run a task

This call runs (“executes”) the specified task. Only tasks with a “DRAFT” status may be run.

tsk$run()
# run update without information just return latest information
tsk$update()

### Monitor a running task and set the hook function

To monitor a running task, call monitor from a Task object.

• The first argument sets the interval time to check the status
• Rest of the arguments might be used for the hook function

tsk$monitor()

Get and set default a hook function for task status. Currently, failed tasks will break the monitoring.

Note: Hook function has to return TRUE (break monitoring) or FALSE (continuing) in the end.

getTaskHook("completed")
getTaskHook("draft")
setTaskHook("draft", function() {
  message("never happens")
  return(TRUE)
})
getTaskHook("draft")

3.12.5 Abort a running task

This call aborts the specified task. Only tasks whose status is “RUNNING” may be aborted.

# abort
tsk$abort()
# check
tsk$update()

3.12.6 Delete a task

Note that you can only delete DRAFT tasks, not running tasks.

tsklst <- a$task(status = "draft")
# delete a single task
tsklst[[1]]$delete()
# confirm
a$task(status = "draft")
# delete a list of tasks
delete(tsklst)

3.12.7 Download all files from a completed task

tsk$download("~/Downloads")

3.12.8 Run tasks in batch mode

To run tasks in batch mode, (check ?batch) for more details. The code below is a mockup example.

# batch by items
(tsk <- p$task_add(
  name = "RNA DE report new batch 2",
  description = "RNA DE analysis report",
  app = rna.app$id,
  batch = batch(input = "bamfiles"),
  inputs = list(
    bamfiles = bamfiles.in,
    design = design.in,
    gtffile = gtf.in
  )
))

# batch by metadata, input files has to have metadata fields specified
(tsk <- p$task_add(
  name = "RNA DE report new batch 3",
  description = "RNA DE analysis report",
  app = rna.app$id,
  batch = batch(
    input = "fastq",
    c("metadata.sample_id", "metadata.library_id")
  ),
  inputs = list(
    bamfiles = bamfiles.in,
    design = design.in,
    gtffile = gtf.in
  )
))

3.13.1 Create a volume

a <- Auth(user = "RFranklin", platform = "aws-us")

a$add_volume(
  name = "tutorial_volume",
  type = "s3",
  bucket = "RFranklin-demo",
  prefix = "",
  access_key_id = "your_access_key_id",
  secret_access_key = "your_secret_access_key",
  sse_algorithm = "AES256",
  access_mode = "RW"
)

3.13.2 List and search all volumes

# list all volume
a$volume()
# get unique volume by id
a$volume(id = "RFranklin/RFranklin_demo")
# partial search by name
a$volume(name = "demo")

3.13.3 Get a volume’s detail

v <- a$volume()
v[[1]]$detail()

3.13.4 Delete volume

This call deletes a volume you’ve created to refer to storage on Amazon Web Services or Google Cloud Storage.

Note that any files you’ve imported from your volume onto a Seven Bridges environment, known as an alias, will no longer be usable. If a new volume is created with the same volume_id as the deleted volume, aliases will point to files on the newly created volume instead (if those exist).

a$volume(id = "RFranklin/RFranklin_demo")$delete()

3.13.5 Import file from volume to project

This call imports a file from volume to your project.

v <- a$volume(id = "RFranklin/tutorial_volume")
res <- v$import(
  location = "A-RNA-File.bam.bai",
  project = "RFranklin/s3tutorial",
  name = "new.bam.bai",
  overwrite = TRUE
)

# get job status update
# state will be "COMPLETED" when it's finished, otherwise "PENDING"
v$get_import_job(res$id)
v

3.13.6 Export file from project to volume

Important :

• The file selected for export must not be a public file or an alias. Aliases are objects stored in your cloud storage bucket which have been made available on a Seven Bridges environment. The volume you are exporting to must be configured for read-write access. To do this, set the access_mode parameter to RW when creating or modifying a volume.
• If this call is successful, the original project file will become an alias to the newly exported object on the volume. The source file will be deleted from the Seven Bridges environment and, if no more copies of this file exist, it will no longer count towards your total storage price on the Seven Bridges environment.

When testing, please update your file in a project.

res <- v$export(
  file = "579fb1c9e4b08370afe7903a",
  volume = "RFranklin/tutorial_volume",
  location = "", # when "" use old name
  sse_algorithm = "AES256"
)
# get job status update
# state will be "COMPLETED" when it's finished other wise "PENDING"
v$get_export_job(res$id)
v

3.14.1 Public files

# list the first 100 files
a$public_file()
# list by offset and limit
a$public_file(offset = 100, limit = 100)
# simply list everything!
a$public_file(complete = TRUE)
# get exact file by id
a$public_file(id = "5772b6f0507c175267448700")
# get exact file by name with exact = TRUE
a$public_file(name = "G20479.HCC1143.2.converted.pe_1_1Mreads.fastq", exact = TRUE)
# with exact = FALSE by default search by name pattern
a$public_file(name = "fastq")
a$public_file(name = "G20479.HCC1143.2.converted.pe_1_1Mreads.fastq")

Public files are hosted in the project called admin/sbg-public-data, and you can alternatively use the file request to get files you need.

3.14.2 Public apps

For public apps, there are similar API calls.

# list for 100 apps
a$public_app()
# list by offset and limit
a$public_app(offset = 100, limit = 50)
# search by id
a$public_app(id = "admin/sbg-public-data/control-freec-8-1/12")
# search by name in ALL apps
a$public_app(name = "STAR", complete = TRUE)
# search by name with exact match
a$public_app(name = "Control-FREEC", exact = TRUE, complete = TRUE)

3.15.1 Copy files between projects

This call allows you to copy files between projects. Unlike a$copyFile() or file(...)$copyTo(...) which only copy one file with each API call, this call lets you batch the copy operation and copy a list of files at a time.

p <- a$project(id = "RFranklin/source-project")
f <- p$file(complete = TRUE)
# get all file IDs
file_ids <- sapply(f, "[[", "id")
# bulk copy files to the target project
req <- a$bulk_file_copy(file_ids, "RFranklin/target-project")
# print the response list
(req <- unname(req))

[[1]]
[[1]]$status
[1] "OK"

[[1]]$new_file_id
[1] "5bf31316e4b09b8ff39f9df7"

[[1]]$new_file_name
[1] "merged-tumor.converted.pe_1.fastq"

...

We can use sapply to get the copy operation status, new file IDs, and (new) file names for the copied files:

sapply(req, "[[", "status")

[1] "OK" "OK" "OK" "OK"

sapply(req, "[[", "new_file_id")

[1] "5bf31316e4b09b8ff39f9df7" "5bf31316e4b09b8ff39f9dfa" "5bf31316e4b09b8ff39f9df4" "5bf31316e4b09b8ff39f9df1"

sapply(req, "[[", "new_file_name")

[1] "merged-tumor.converted.pe_1.fastq"  "merged-tumor.converted.pe_2.fastq"  "merged-normal.converted.pe_2.fastq"
[4] "merged-normal.converted.pe_1.fastq"

Note that a file’s ID is dependent on the project it is contained in. So, when you copy files from one project to another, their IDs will be different in the target project. The file names, however, do not change by copying, except where copying would yield non-unique file names in the target project.

3.15.2 Send a feedback item

Use this call to send feedbacks to Seven Bridges via the API. There are three feedback types available: "idea", "thought", or "problem". You can send one feedback item per minute.

a$send_feedback(
  "This is a test for sending feedback via API. Please ignore this message.",
  type = "thought"
)

3.16.1 API token for the division context

Note that the authentication token for the Enterprise API is a separate token generated under the context of your division, which is different from your non-division (personal) auth token. You may see the following error when using the non-division token to call the Enterprise API:

Error: HTTP Status 400: Insufficient privileges to access this resource. Not a division user.

If you see this error, first switch to the correct division context (use the dropdown menu in the upper left corner), then click the “Developer” tab, click “Auth token”, generate the token, and use this token for API authentication.

3.16.2 List all divisions

To list all divisions you have access to, use

a <- Auth(...)

a$division()

[[1]]
== Division ==
  id : the-division
name : The Division
[[2]]
== Division ==
  id : another-division
name : Another Division

3.16.3 Get details of a division

To get the details (ID and name) of a division, for example, the first division listed above, use

(d <- a$division("the-division"))

== Division ==
  id : the-division
name : The Division

3.16.4 Create a team

Let’s create two new teams under this division:

team1 <- d$create_team(name = "New Team 1")
team2 <- d$create_team(name = "New Team 2")

3.16.5 Get details of a team

To check the details (ID and name) of the first team we just created, use

d$team(team1$id)

== Team ==
id : 39f6cb44-9e3c-40e7-8639-3c0f3c1e4892
name : New Team 1

3.16.6 Add a team member

We can add division members to the teams we created. For example, let’s add yourself (with the division username the-division/your_username) and another division member (with the division username the-division/another_username) to the first team. Also, let’s add yourself to the second team:

team1$add_member("the-division/your_username")
team1$add_member("the-division/another_username")

team2$add_member("the-division/your_username")

3.16.7 List team members

List all team members and their roles:

(m1 <- team1$member())
(m2 <- team2$member())

[[1]]
== Team Member ==
username : the-division/another_username
role : ADMIN
[[2]]
== Team Member ==
username : the-division/your_username
role : ADMIN

[[1]]
== Team Member ==
username : the-division/your_username
role : ADMIN

3.16.8 Remove a team member

Let’s remove a user from the first team:

team1$remove_member(m1[[1]]$username)

3.16.9 Rename a team

To rename a team, use:

team1$rename("Another Team Name")

== Team ==
id : 39f6cb44-9e3c-40e7-8639-3c0f3c1e4892
name : Another Team Name

After renaming, the team will still have the same ID, just with a different name.

3.16.10 List your teams in the division

To list the teams that you are a member of in a division, use

d$team()

Note that there could be a one-minute delay in the backend here if you just added yourself to the teams seconds ago.

3.16.11 Delete a team

To delete the teams we created, use

team1$delete()
team2$delete()

3.17.1 Create a marker

Let’s create a new marker on a BAM file first:

# locate the project
p <- a$project(id = "RFranklin/api-markers")
# search for files with `.bam` in their names
f <- p$file(name = ".bam")
# use the first BAM file
f <- p$file(id = f[[1]]$id)

# create two markers
m1 <- f$create_marker("The First Marker", start = 21631232, end = 21631232)
m2 <- f$create_marker("The Second Marker", start = 21631156, end = 21631158, chromosome = "chr7", private = FALSE)

The possible parameters for creating the marker include

• The marker’s name (name)
• The marker’s position (start and end)
• Chromosome number (chromosome)
• Whether the marker is private or public (private).

The marker’s name and its position are mandatory parameters, and the others are optional.

3.17.2 List markers available on a file

To list all markers on a file, use:

f$marker()

[[1]]
== Marker ==
id : 5bf478e5d38f185f0c23bc44
name : The First Marker
[[2]]
== Marker ==
id : 5bf478e6d38f185f0c23bc45
name : The Second Marker

3.17.3 Get details for a marker

We can also check the details for a specific marker:

marker_id <- m1$id
f$marker(id = marker_id)

== Marker ==
id : 5bf478e5d38f185f0c23bc44
name : The First Marker
file : 5bf46c1be4b39b8f5232282e
position:
  start : 21631232
  end : 21631232
created_time : 2018-11-20T21:13:00Z
created_by : RFranklin
private : TRUE

3.17.4 Modify a marker

We can also modify the information of existing markers:

(m1 <- m1$modify(name = "New Marker Name", end = 21631233, private = FALSE))

== Marker ==
id : 5bf478e5d38f185f0c23bc44
name : New Marker Name
file : 5bf46c1be4b39b8f5232282e
position:
  start : 21631232
  end : 21631233
created_time : 2018-11-20T21:13:00Z
created_by : RFranklin
private : FALSE

All of the five marker parameters mentioned above can be modified.

3.17.5 Delete a marker

To delete the markers we just added, use

m1$delete()
m2$delete()