You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -16,53 +16,6 @@ HistoJS is an interactive tool to manage, store and analysis the multi-channels
16
16
17
17
The tool is using Digital Slide Archive as a backbone to update the image metadata remotely or locally.
18
18
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:
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
-
66
19
67
20
68
21
## Offline Demo
@@ -81,8 +34,8 @@ For creating OME channel groups, browse to your server file and click design mod
*[Your First Code Contribution](#your-first-code-contribution)
16
-
13
+
*[Pull Requests](#pull-requests)
17
14
18
15
19
16
20
17
## Code of Conduct
21
18
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).
23
20
24
21
## Having a question?
25
22
26
23
> **Note:** Please don't file an issue to ask a question. You'll get faster results by using the resources below.
@@ -67,7 +53,7 @@ Bugs are tracked as [GitHub issues](https://guides.github.com/features/issues/).
67
53
68
54
Include details about your configuration and environment:
69
55
70
-
***Which version of OS, Browser, GPU, CPU you are using**?
56
+
***Which version of OS, Browser, GPU, CPU are you using**?
71
57
***What size of RAM you are using**?
72
58
***Which model you used with the problem**?
73
59
@@ -81,9 +67,9 @@ Include details about your configuration and environment:
81
67
82
68
Please follow these steps to have your contribution considered by the maintainers:
83
69
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
87
73
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>
88
74
89
75
5. Don't delete your forked repository until your pull request approved and merged.
0 commit comments