Skip to content

Commit 5d7ccae

Browse files
committed
v1.0.0
1 parent e5cd716 commit 5d7ccae

File tree

2 files changed

+18
-79
lines changed

2 files changed

+18
-79
lines changed

README.md

Lines changed: 3 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
[![HistoJS logo](https://lh3.googleusercontent.com/Q3eYJfpQMety3sUUTLKeZKLkJBzx-NmLZNn1NphdWs9hBNYmfHCzZTphddpXDcfUxjtaHTXTr89R57LieZflqUsGHM3TxtIbVNoQOKf3ZbPjB01C8gYANmezAzq4JgUU=w1823)]()
66

7-
[![Github contributors](https://img.shields.io/badge/contributors-*-brightgreen)](https://github.com/Mmasoud1/HistoJS/graphs/contributors) [![licence ](https://img.shields.io/badge/license-BY--NC--ND-orange)](https://creativecommons.org/licenses/by-nc-nd/3.0/) [![Python ](https://img.shields.io/badge/python-3.5%20%7C%203.6%20%7C%203.7-blue)]()[![JS ](https://img.shields.io/badge/Types-JavaScript-blue)]()
7+
[![MIT-License ](https://img.shields.io/badge/license-MIT-green)](https://github.com/Mmasoud1/HistoJS/blob/main/LICENSE) [![Python ](https://img.shields.io/badge/python-3.5%20%7C%203.6%20%7C%203.7-blue)]()[![JS ](https://img.shields.io/badge/Types-JavaScript-blue)]()
88
[![HW ](https://img.shields.io/badge/HardWare-GPU-green)]()
99

1010

@@ -16,53 +16,6 @@ HistoJS is an interactive tool to manage, store and analysis the multi-channels
1616

1717
The tool is using Digital Slide Archive as a backbone to update the image metadata remotely or locally.
1818

19-
- Install requirements
20-
```bash
21-
3.4 < python < 3.8 is recommended
22-
```
23-
24-
```bash
25-
conda env create -f histojs.yml
26-
```
27-
28-
29-
30-
31-
After creating the histojs environment, from the root level of the repository open a new terminal, activate the env and run the python ResApi file:
32-
33-
```bash
34-
source activate histojs
35-
python RestApi.py
36-
```
37-
38-
To run the localhost in the browser, just start up a simple local server from the root level of the repository with any available port number 8xxx (e.g. 8020)
39-
40-
```bash
41-
python -m http.server 8xxx
42-
```
43-
44-
45-
-In the browser url type:
46-
47-
```bash
48-
http://localhost:8020/
49-
```
50-
51-
52-
53-
A dockerized version will be released soon for the api.
54-
55-
For using the backbone DSA server, you need to create a user account on any DSA servers and upload your OME image, cells mask, and channels metadata CSV file to your collection as in this link:
56-
57-
```bash
58-
https://styx.neurology.emory.edu/girder/#folder/5e361c5c34679044bda81b11
59-
```
60-
61-
62-
Please note: if the name of the OME image file is $fileName$.ome.tif (e.g. TONSIL-1_40X.ome.tif), the cell mask must be $fileName$_cellMask.tiff (e.g. TONSIL-1_40X_cellMask.tiff), and the Channel metadata CSV file should be $fileName$_channel_metadata.csv (e.g. TONSIL-1_40X_channel_metadata.csv)
63-
64-
The Channel metadata CSV file must have at least two columns: 'channel_number' and 'channel_name'
65-
6619

6720

6821
## Offline Demo
@@ -81,8 +34,8 @@ For creating OME channel groups, browse to your server file and click design mod
8134

8235
<div align="center">
8336

84-
[![Google Doc](https://img.shields.io/badge/HistoJS-Feedback-blue)](https://docs.google.com/forms/d/e/1FAIpQLSdHuO--mG00sKydQpJ7sPpDmhcJ4ECdj-wAB1kwXQExh_nUSg/viewform?usp=sf_link)[![CC BY-NC-ND ](https://img.shields.io/badge/license-BY--NC--ND-orange)](https://creativecommons.org/licenses/by-nc-nd/3.0/)
37+
[![Google Doc](https://img.shields.io/badge/HistoJS-Feedback-blue)](https://docs.google.com/forms/d/e/1FAIpQLSdHuO--mG00sKydQpJ7sPpDmhcJ4ECdj-wAB1kwXQExh_nUSg/viewform?usp=sf_link) [![MIT-License ](https://img.shields.io/badge/license-MIT-green)](https://github.com/Mmasoud1/HistoJS/blob/main/LICENSE)
8538

86-
**Copyright 2021 Mohamed Masoud**
39+
**Copyright 2023 Mohamed Masoud**
8740
</div>
8841

docs/CONTRIBUTING.md

Lines changed: 15 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -1,55 +1,41 @@
1-
Thank you for taking the time to contribute to Brainchop!.
1+
Welcome again to HistoJS, and thank you for taking the time to contribute!
22

33
The following is our set of guidelines to ease your contribution.
44

55
#### Table Of Contents
66

77
[Code of Conduct](#code-of-conduct)
88

9-
[Having a Question](#Having-a-question)
10-
11-
[ Project Structure ](#Project-Structure)
12-
139
[How To Contribute?](#how-can-i-contribute)
1410
* [Reporting Bugs](#reporting-bugs)
11+
* [Suggesting Enhancements](#suggesting-enhancements)
1512
* [Your First Code Contribution](#your-first-code-contribution)
16-
13+
* [Pull Requests](#pull-requests)
1714

1815

1916

2017
## Code of Conduct
2118

22-
This project and everyone participating in it is governed by the [Code of Conduct](https://github.com/neuroneural/brainchop/wiki/CODE-OF-CONDUCT). By participating, you are expected to uphold this code. Please report unacceptable behavior to [brainchop@github.com](mailto:brainchop@github.com).
19+
This project and everyone participating in it is governed by the [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [HistoJS@github.com](mailto:HistoJS@github.com).
2320

2421
## Having a question?
2522

2623
> **Note:** Please don't file an issue to ask a question. You'll get faster results by using the resources below.
2724
28-
* [Brainchop Discussions Board](https://github.com/neuroneural/brainchop/discussions)
29-
* [Brainchop Q&A](https://github.com/neuroneural/brainchop/discussions/categories/q-a)
25+
* [HistoJS Discussions Board](https://github.com/HistoJS/HistoJS/discussions)
26+
* [HistoJS FAQ](wiki/faq/)
3027

3128

32-
33-
## Project Structure
29+
### Project Structure
3430

3531
* **Root**
3632
* style
3733
* lib
3834
* js
39-
* mainMeshNetFunctions.js ( Brainchop main functions)
40-
* mainNiftiReadingFunctions.js (Nifti functions)
41-
* mainParameters.js
42-
* python
43-
* MRI (data)
44-
* ExperimentalMode
45-
* ModelToLoad (Models)
46-
* model11_gw_ae
47-
* colorLUT.json (Seg ROI Color Data)
48-
* labels.json (Seg ROI Labels)
49-
* group1-shard1of1.bin (Model Weights Binary file)
50-
* model.json (Model JSON file)
51-
52-
35+
* css
36+
* features
37+
* boundaries
38+
5339

5440
## How Can I Contribute?
5541

@@ -67,7 +53,7 @@ Bugs are tracked as [GitHub issues](https://guides.github.com/features/issues/).
6753

6854
Include details about your configuration and environment:
6955

70-
* **Which version of OS, Browser, GPU, CPU you are using**?
56+
* **Which version of OS, Browser, GPU, CPU are you using**?
7157
* **What size of RAM you are using**?
7258
* **Which model you used with the problem**?
7359

@@ -81,9 +67,9 @@ Include details about your configuration and environment:
8167

8268
Please follow these steps to have your contribution considered by the maintainers:
8369

84-
1. Fork Brainchop repository to have a copy on your github.
85-
2. Push your updates to the forked Brainchop repository on your github.
86-
3. Into your forked Brainchop repository create a pull request, it should show you the base repository (original one) and the head repository (forked one), choose master branch for each and create pull request
70+
1. Fork HistoJS repository to have a copy on your github.
71+
2. Push your updates to the forked HistoJS repository on your github.
72+
3. Into your forked HistoJS repository create a pull request, it should show you the base repository (original one) and the head repository (forked one), choose master branch for each and create pull request
8773
4. After you submit your pull request, verify that all [status checks](https://help.github.com/articles/about-status-checks/) are passing <details><summary>What if the status checks are failing?</summary>If a status check is failing, and you believe that the failure is unrelated to your change, please leave a comment on the pull request explaining why you believe the failure is unrelated. A maintainer will re-run the status check for you. If we conclude that the failure was a false positive, then we will open an issue to track that problem with our status check suite.</details>
8874

8975
5. Don't delete your forked repository until your pull request approved and merged.

0 commit comments

Comments
 (0)