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
Copy file name to clipboardexpand all lines: README.md
+26-5
Original file line number
Diff line number
Diff line change
@@ -10,42 +10,60 @@
10
10
API specification for deploy the [detection models](https://github.com/RentadroneCL/model-definition/blob/master/README.md), this repository contains a performant, production-ready reference implementation.
11
11
12
12
## Documentation
13
+
13
14
See [https://rentadronecl.github.io/docs](https://rentadronecl.github.io/docs/detection-models) for tutorials and more guides.
14
15
15
16
## Developers
17
+
16
18
Help improve our software! We welcome contributions from everyone, whether to add new features, improve speed, fix existing bugs or add support. [Check our code of conduct](CODE_OF_CONDUCT.md), [the contributing guidelines](CONTRIBUTING.md) and how decisions are made.
17
19
18
20
Any code contributions are welcomed as long as they are discussed in [Github Issues](https://github.com/RentadroneCL/Web-API/issues) with maintainers. Be aware that if you decide to change something and submit a PR on your own, it may not be accepted.
19
21
20
-
#### Creating an issue
21
-
You can open a new issue based on code from an existing pull request. For more information, see [the template for filling issues](https://github.com/RentadroneCL/Web-API/blob/master/.github/ISSUE_TEMPLATE/feature_request.md)
22
+
### Creating an issue
23
+
24
+
To encourage active collaboration, we strongly encourages pull requests, not just bug reports. "Bug reports" may also be sent in the form of a pull request containing a failing test.
25
+
26
+
However, if you file a bug report, your issue should contain a title and a clear description of the issue. You should also include as much relevant information as possible and a code sample that demonstrates the issue. The goal of a bug report is to make it easy for yourself - and others - to replicate the bug and develop a fix. For more information, see the templates for filling issues.
27
+
28
+
| Template | Description | Example |
29
+
| -------- | ------------|---------|
30
+
| Feature request | Suggest an idea for this project |[template](https://github.com/RentadroneCL/Web-API/blob/master/.github/ISSUE_TEMPLATE/feature_request.md)|
31
+
| Bug report | Create a report to help us improve |[template](https://github.com/RentadroneCL/Web-API/blob/master/.github/ISSUE_TEMPLATE/bug_report.md)|
32
+
33
+
Remember, bug reports are created in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the bug report will automatically see any activity or that others will jump to fix it. Creating a bug report serves to help yourself and others start on the path of fixing the problem. If you want to chip in, you can help out by fixing any bugs listed in our [issue trackers](https://github.com/RentadroneCL/Web-API/issues).
22
34
23
35
## Requirements
36
+
24
37
Python 3.6+
25
38
26
39
## Quickstart
40
+
27
41
In the root project execute the following command to install all dependencies project
28
42
29
-
```
43
+
```bash
30
44
pip install -r requirements.txt
31
45
```
32
46
33
-
You will also need an ASGI server, for production such as <ahref="http://www.uvicorn.org"class="external-link"target="_blank">Uvicorn</a> or <ahref="https://gitlab.com/pgjones/hypercorn"class="external-link"target="_blank">Hypercorn</a>.
47
+
You will also need an ASGI server, for production such as [Uvicorn](http://www.uvicorn.org)or [Hypercorn](https://gitlab.com/pgjones/hypercorn).
34
48
35
49
```bash
36
50
pip install uvicorn
37
51
```
38
52
39
53
## Configuration
54
+
40
55
### Configuration Files
56
+
41
57
All of the configuration files for the API are stored in the `config` directory. Each option is documented, so feel free to look through the files and get familiar with the options available to you.
42
58
43
59
### Application Key
60
+
44
61
The next thing you should do after installing is set your application key to a random string.
45
62
46
63
Typically, this string should be 32 characters long. The key can be set in the `.env` environment file. If you have not copied the `.env.example` file to a new file named `.env`, you should do that now. If the application key is not set, your user sessions and other encrypted data will not be secure!
47
64
48
65
### Model Configuration
66
+
49
67
The model that we are going to deploy is for predicting photovoltaic fault. You can get the data [here](https://drive.google.com/drive/folders/1LSc9FkAwJrAAT8pAUWz8aax_biFAMMXS?usp=sharing).
50
68
51
69
| Model | Weights Trained | Config |
@@ -60,6 +78,7 @@ The model that we are going to deploy is for predicting photovoltaic fault. You
60
78
We start by loading the data and compiled models into the `storage/model` folder and the configuration files for each model in the `storage/config` folder and saving the names of the features that we want to use in our model.
61
79
62
80
### Example model configuration file
81
+
63
82
```js
64
83
{
65
84
"model": {
@@ -74,7 +93,7 @@ We start by loading the data and compiled models into the `storage/model` folder
74
93
75
94
After we have prepared the data and saved all necessary files it is time to start creating the API to serve our model from.
76
95
77
-
**NOTE:** There are several methods for saving a model, each with its own sets of pros and cons you may change in function of your necesities.
96
+
**NOTE:** There are several methods for saving a model, each with its own sets of pros and cons you may change in function of your necessity.
78
97
79
98
### Run it
80
99
@@ -103,6 +122,7 @@ You already created an API that:
103
122
* If the mimetype does not indicate JSON `application/json` this returns `None`.
104
123
105
124
### Example of an input data
125
+
106
126
```js
107
127
[
108
128
{
@@ -137,6 +157,7 @@ You already created an API that:
0 commit comments