Project gregoryonline
experimental code to online survey root spectra from THTTPServer
Last notice: changing to keybssh NOW
Usage
Based on ~/.config/gregoryonline/cfg.json
{
"placeholder": true,
"filename": "~/.config/gregory_online/cfg.json",
"spectrum": "b0c00",
"udp_ip": "127.0.0.1",
"server": "x.x.x.x",
"poll_time": 5
}
it connects to
./bin_gregory_online.py
# OR override the server and spectrum name
./bin_gregory_online.py -s 127.0.0.1 -h b0c00
Install
Github? pip3 in future
UI Components
There are two:
- topbar
- keyenter
The topbar runs in the background, provides two bars. The second one is the keyboard input bar.
Engines of fetch
- keep getting histo from server
- keep historical spectra and be prepared to show dif
- keep track of age and show rate
- show bg spectrum rate for comparison
Version 2
histoglobalcont.py Container for histograms
histonpops.py operations between np ad th1
histoio.py load and save
bingregoryonline.py
config.py
fetchnp.py
getspe.py
keyenter.py
mockserver.py
rebin.py
setup.py
topbar.py
utilone.py
version.py
Metadata
Release files for gregory-online 0.3.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gregory_online-0.3.7.tar.gz | 690.6 kB | Without provenance | Details for gregory_online-0.3.7.tar.gz |
Release files / gregory_online-0.3.7.tar.gz
| Download URL | gregory_online-0.3.7.tar.gz |
|---|---|
| Size | 690.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ffd510ae4408ce3653a333d7faf1c1a797c00f50ba04acd15bac3fb1c7f52732
|
|
BLAKE2b-256 checksum How to use checksums |
d697835a781ab8710fb6afa0c1c90e0871cecf7fac734c9ddf66a9bc82a73101
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Security for gregory-online 0.3.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.