MPIIComputationalEpigenetics / DeepBlue

DeepBlue Epigenomic Data Server
Other
2 stars 0 forks source link

Provide direct access to matched controls #85

Closed ghost closed 8 years ago

ghost commented 9 years ago

Not sure if that info is somewhere in a "parsable" format, but it would be very convenient if there was an API function that provides the user with the matched control experiment (or none) for ChIP-seq data.

For ENCODE data, one example would be ENCFF001FOA (raw signal for H3K4me3 in epithelial cells) and ENCFF001HPK (the raw signal of the control track).

Workflow:

# for control data, there is only a signal track, no peaks, so this should return something unique
stat, res = srv_api.get_matched_control('expname_of_chipseq', user_key)
print(res)
expname_of_matched_control
felipealbrecht commented 8 years ago

Honestly I do not want to implement a function like this because it is straighforward to do in Python or R:

This R code for ENCODE experiments:

experiment_id = deepblue_name_to_id("ENCFF001FOA", "experiments")[[1]][[1]]
sample_id = deepblue_info(experiment_id)[[1]]$sample_id
control_experiment = deepblue_list_experiments(sample=sample_id, epigenetic_mark="Control")