akmorrow13

Hi @kevinyao93 ! All the code for handling the range change happens [here](https://github.com/hammerlab/pileup.js/blob/master/src/main/Root.js#L59). You can thus track the state of the [range in Root.js](https://github.com/hammerlab/pileup.js/blob/master/src/main/Root.js#L24) to detect when the range changes.

Hi @Parul-Kudtarkar, We are very open to community contributions! What particular type of track are you interested in adding?

Yes that would be excellent! @Parul-Kudtarkar what file types store chromatin interactions?

Ok. The .bed format may be easiest. We currently do not have a DataSource for bed or ChIA-PET. We do, however, support bigbed files. We have been meaning to add...

Unfortunately due to loss of man power adding bed support has completely dropped off the table because we already support bigbed files. However, if you can implement the chromatin interaction...

Hi @jodyphelan, to answer your questions: 1. There is unfortunately no documentation, although that is very needed. 2. Can you link to the issue that discussed how to change these...

@denisemauldin you can run the tests interactively by running the http server and going to test-runner (instructions here). ``` npm run http-server open http://localhost:8080/src/test/runner.html ``` I am not sure if...

@denisemauldin travis runs remotely so you can not run it locally. However, you can run all of the commands that travis runs, listed in the [.travis.yml file](https://github.com/hammerlab/pileup.js/blob/master/.travis.yml). It looks like...

The only feature files that pileup.js supports is BigBed ([Here is an example of viewing Genes with BigBed,](https://github.com/hammerlab/pileup.js/blob/master/examples/data.js#L45) but you can substitute the `pileup.viz.genes()` with `pileup.viz.features()` for viewing features) There...

Any ideas on how to access environment variables in .gin files?