guidelines-for-methods
Methods Hub's Guidelines for Methods
Science Score: 44.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Committers with academic emails
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (14.9%) to scientific vocabulary
Repository
Methods Hub's Guidelines for Methods
Basic Info
- Host: GitHub
- Owner: GESIS-Methods-Hub
- License: cc0-1.0
- Default Branch: main
- Homepage: https://git.gesis.org/methods-hub/guidelines-for-tutorials
- Size: 182 KB
Statistics
- Stars: 1
- Watchers: 4
- Forks: 3
- Open Issues: 0
- Releases: 0
Metadata Files
README-template.md
README Template: Specification and Illustration of the Methods Hub Friendly README
Description
METHOD allows to do XXX.
METHOD takes XXX in XXX format as input and provides XXX in XXX format as output. Alternatively, METHOD can also be configured to XXX. METHOD works with XXX data. METHOD can use any XXX-compatible API. The output of METHOD is compatible with XXX.
METHOD placed Xth in the XXX competition on XXX. METHOD is much faster than other methods. METHOD runs quickly on standard hardware. METHOD requires a GPU.
Use Cases
- A XXX wants to do XXX. Their situation is that XXX. They use METHOD by doing XXX to do XXX, which solves their original problem because XXX.
Example publications that illustrate this use case:
- XXX.
- XXX.
Input Data
METHOD takes as input XXX in XXX format and XXX in XXX format.
Example input data XXX (excerpt of example-input-file1.json):
{json}
{
"key": [
"value [...]"
],
"key": "value"
}
key. A list of XXX. If missing or empty, then XXX.key. XXX. One of XXX, XXX, or XXX. If missing, then XXX.key. XXX. A number between XXX and XXX. If missing, then XXX.key. XXX. Required.
Example input data XXX (one line of example-input-file2.ndjson, formatted for readability):
{json}
{
"key": [
"value [...]"
]
}
key. XXX.
Output Data
METHOD produces XXX in XXX format. The README template produces a README according to the Methods Hub friendly README specification.
Example output data (excerpt of example-output-file.csv):
{csv}
header 1,header 2
value 1-1,value 1-2
value 2-1,value 2-2
Hardware Requirements
METHOD runs on a cheap virtual machine provided by cloud computing company (2 x86 CPU core, 4 GB RAM, 40GB HDD). METHOD requires a GPU (compute capability XXX, XXX GB VRAM) to run.
Environment Setup
METHOD requires at least XXX version XXX. To avoid problems with your system's Python installation, create and activate a virtual environment.
METHOD requires an XXX API key. Get one here and paste it into example-key-file.txt. METHOD requires XXX in directory XXX. Download it from here.
Then install all requirements using:
{bash}
pip install -r requirements.txt
Then install METHOD in R using:
{R}
install.packages("METHOD")
How to Use
To apply METHOD to the example input and generate the example output, proceed as follows:
{bash}
python method.py example-input-file1.json example-input-file2.ndjson
To adapt these steps to your needs, see the online documentation of METHOD.
To adapt these steps to your needs, see the output of python method.py --help.
To adapt these steps to your needs, adapt the configuration file:
xxx: Controls XXX. (default: "XXX")
To adapt these steps to your needs, apply the following command line parameters:
--xxx: Controls XXX. (default: "XXX")
To adapt these steps to your needs, adapt the configuration file or apply the following command line parameters (overwriting respective settings in the configuration file):
--xxx: Controls XXX. (default: "XXX")
Technical Details
METHOD does XXX by performing the following steps:
- Reading. The data is read from the input file (
--input-file) and converted into XXX. (see method-package/example-source-file.py) - Downloading data. XXX data is fetched from XXX.
- XXX. To do XXX, the method uses XXX with XXX set to XXX (change using
--xxxor settingxxxin the configuration file). (see method-package/example-source-file.py) - Writing. The result is written to the output file (
--output-file). (see method-package/example-source-file.py)
See the publication for tested and selected models and parameters, the reasoning behind the model selection, and employed datasets for training.
References
- Dataset used for training:
XXX.
- Employed model:
XXX.
- Underlying infrastructure:
XXX.
Acknowledgements
Special thanks to the creators of XXX for providing XXX. Special thanks to XXX for XXX.
Disclaimer
METHOD is intended for academic research, and users are responsible for ensuring the legality and ethicality of their data use. Ensure you follow the XXX Terms of Service when using this method.
Contact Details
In case of questions, contact XXX. For contributions and bug reports, open an issue at XXX.
Owner
- Name: GESIS-Methods-Hub
- Login: GESIS-Methods-Hub
- Kind: organization
- Repositories: 1
- Profile: https://github.com/GESIS-Methods-Hub
Citation (CITATION.cff)
cff-version: 1.2.0
title: Methods Hub's Guidelines for Methods
message: >-
If you want to cite these guidelines, please cite it as below.
type: software
authors:
- name: Methods Hub Team
website: >-
https://www.gesis.org/en/services/processing-and-analyzing-data/analyzing-digital-behavioral-data/gesis-methods-hub
email: methodshub@gesis.org
repository-code: >-
https://github.com/GESIS-Methods-Hub/guidelines-for-methods
license: CC0-1.0
GitHub Events
Total
- Issues event: 10
- Delete event: 4
- Issue comment event: 8
- Push event: 88
- Pull request review comment event: 33
- Pull request event: 5
- Pull request review event: 13
- Fork event: 3
- Create event: 4
Last Year
- Issues event: 10
- Delete event: 4
- Issue comment event: 8
- Push event: 88
- Pull request review comment event: 33
- Pull request event: 5
- Pull request review event: 13
- Fork event: 3
- Create event: 4
Committers
Last synced: over 1 year ago
Top Committers
| Name | Commits | |
|---|---|---|
| Taimoor Khan | 7****p | 44 |
| chainsawriot | c****y@g****m | 1 |
| Raniere Silva | R****a@g****g | 1 |
Committer Domains (Top 20 + Academic)
Issues and Pull Requests
Last synced: 8 months ago
All Time
- Total issues: 6
- Total pull requests: 6
- Average time to close issues: 6 days
- Average time to close pull requests: 12 days
- Total issue authors: 3
- Total pull request authors: 3
- Average comments per issue: 1.0
- Average comments per pull request: 0.5
- Merged pull requests: 3
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 6
- Pull requests: 6
- Average time to close issues: 6 days
- Average time to close pull requests: 12 days
- Issue authors: 3
- Pull request authors: 3
- Average comments per issue: 1.0
- Average comments per pull request: 0.5
- Merged pull requests: 3
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- johanneskiesel (3)
- rgaiacs (2)
- cviehmann (1)
Pull Request Authors
- rgaiacs (4)
- TomatenMarc (1)
- taimoorkhan-nlp (1)