njiang
commented
9 years ago Go to a TB module page such as: http://networks.systemsbiology.net/mtb/biclusters/bicluster_0001
Chrome goose will recognize the data on the page. Select "MTB filtering" from the Data Processing/Filter menu. Then in the dialog box, select the bicluster genes as input and click "run". The data will be passed to the opencpu server. Once it is finished, results will be passed to the "handleGooseData" function. We can then add the data to the module page and render them.
dsalvanha
Ok. The scenario we have now demands us to have some updates on already implemented features:
on Module: Module itself has a configuration file that sets all lanes (and its tracks) to be rendered. _IMPORTANT_\ : There can only be 1 Module configuration set at a time !!!!!!! Whenever user wants to open a gene in a different module we NEED to ask WHETHER or not the user wants to change the Configuration.
two scenarios: If the user chooses to change the configuration ALL WINDOWS should change to the new module configuration. (lanes with its tracks) If the user chooses NOT TO change the configuration, the new gene will open with current configuration
on init of each GGBWindow We should have a configuration argument now to GGBWindow
if configuration is empty (most of the time that user does not use chromeGoose) - we open it with default or last state. if configuration is set to a root module item --> we open GGBWindow with all available tracks.
A first thought on this configuration file is:
configuration = { module_item_name:{ Heatmap:{exp1, exp2, exp3}, QuantitativeSegment:{exp4, exp5} } }
With this, we should open GGBWindow with 3 lanes (default, heatmap, quantitativeSegment) and each experiment populated corretly inside each lane
Only a root module item has a configuration and ALL it's sub-module elements follows it
This feature will be REALLY powerfull.