https://github.com/biocypher/dependency-map

https://github.com/biocypher/dependency-map

Science Score: 13.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (11.5%) to scientific vocabulary
Last synced: 9 months ago · JSON representation

Repository

Basic Info
  • Host: GitHub
  • Owner: biocypher
  • Language: Python
  • Default Branch: main
  • Size: 380 KB
Statistics
  • Stars: 3
  • Watchers: 1
  • Forks: 1
  • Open Issues: 0
  • Releases: 0
Created almost 4 years ago · Last pushed over 3 years ago
Metadata Files
Readme

README.md

DepMap-BioCypher

This is the adapter for the BioCypher representation of the Dependency Map dataset. It assumes presence of the raw (v0.5) input data in the data/v0.5/ folder (in the respective subfolders cellModels, compounds, and genes). I made one change to remove a multi-line field from cellModels_all.txt in line 832 (simply removing the newline). The adapter uses the ontological mapping specified in config/schema_config.yaml to assign input data onto the ontological hierarchy supplied by Biolink (flexibly extended using various BioCypher methods).

The adapter (adapter.py) currently only generates neo4j-admin import-ready files via the batch writer class (to biocypher-out or any specified location). Interaction with the graph via the driver will be implemented next. The process can be run using script.py. If all goes well, the output folder will contain a neo4j-admin-import-call.sh file which, when run in the terminal in the database folder, will create a new database under the name specified in the db_name argument of the BioCypherAdapter instantiation in script.py. The database does not need to be running at this point (but it can). However, it is important that the target database (in the current example the one named "import") is either completely empty or does not exist yet.

After import, and in case the database in point did not exist yet, the database can be created and activated in the Neo4j browser with :use system, create database <db_name>, :use <db_name>. At this point, the DBMS needs to be running.

Installation

The project can be installed using poetry:

git clone https://github.com/saezlab/BioCypher git clone https://github.com/saezlab/DepMap-BioCypher cd DepMap-BioCypher poetry install

The installation assumes a clone of the BioCypher repo to be placed in the same parent folder (e.g., /User/GitHub), which is the reason for the first line.

Owner

  • Name: biocypher
  • Login: biocypher
  • Kind: organization

GitHub Events

Total
Last Year

Issues and Pull Requests

Last synced: 10 months ago

All Time
  • Total issues: 1
  • Total pull requests: 1
  • Average time to close issues: 5 days
  • Average time to close pull requests: less than a minute
  • Total issue authors: 1
  • Total pull request authors: 1
  • Average comments per issue: 5.0
  • Average comments per pull request: 0.0
  • Merged pull requests: 1
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 0
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 0
  • Pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • axh24 (1)
Pull Request Authors
  • slobentanzer (1)
Top Labels
Issue Labels
Pull Request Labels

Dependencies

poetry.lock pypi
  • 145 dependencies
pyproject.toml pypi
  • biocypher *
  • bioregistry ^0.6.9
  • isort ^5.10.1
  • python ^3.9
  • snakeviz ^2.1.1