astrobeckit
A small package full of useful little scripts for astro.
Installation
pip install astrobeckit
Usage
[activate python environment]
And then use any of the following commands on the command line.
papergirl
This script will scrape the arxiv new posts page for all the new papers of the day, cross check these against lists of authors and key words that you are interested in and only return those specific papers. It will then email this curated list straight to your inbox. Note that this script requires the following environment variables to be set
PAPERGIRL_PASSWORD # the app specific password
PAPERGIRL_FROM # the email address it should be sent from
PAPERGIRL_TO # the email address it should be sent to
The author and topic lists should also exist even if blank. To run:
papergirl (--topics [location of topics file] --authors [location of authors file])`
synchro
This script creates a file called "splash.filenames" that lists in the correct filenames you need for a synchronised movie with splash. It is designed to be used when you have several simulation folders and for whatever reason the files have gotten out of synch. It requires the log files and a file that lists the folders you are interested in, separated as a new line. To run:
synchro --folders_file [file that lists the folders of interest]
(--prefix [file name prefix, e.g. disc]
--end [when to stop movie])
auto_resubmit
This script is specific to the AVON cluster at Warwick. Looks for all the subfolders in the current directory and resubmits the simulation in there if it hasn't finished. Assumes that the run submission script is called "run_sbatch.sh".
This script also assumes the existance of multi_run.sh, a short script that
generates linked submission jobs. It is also uploaded to this repository but
must be downloaded separately and is assumed to be in ~/runs/. To run:
auto_resubmit (--search_string [masks for a string in the folder names]
--dry_run [if True, just does a test run]
--n_sub [how many linked jobs do you want submitted])
Metadata
Release files for astrobeckit 0.1.4
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 | |
|---|---|---|---|---|
| astrobeckit-0.1.4.tar.gz | 22.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| astrobeckit-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 44.2 kB
Release files / astrobeckit-0.1.4.tar.gz
| Download URL | astrobeckit-0.1.4.tar.gz |
|---|---|
| Size | 22.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f25ef737ff06e0226e40bb27695b1f2352cc7e7aa6c6967d646fa59f41b01dfd
|
|
BLAKE2b-256 checksum How to use checksums |
882191617b2b8b4add1f4c68434293f65121ffbdf3d3662a20d6e42138dbfffe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.11
|
Release files / astrobeckit-0.1.4-py3-none-any.whl
| Download URL | astrobeckit-0.1.4-py3-none-any.whl |
|---|---|
| Size | 22.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e850e7e1fe4e4dcc997484a767a70084b80eb709bcf9635cf49e024221c184a8
|
|
BLAKE2b-256 checksum How to use checksums |
2a3fbd43f5d7e4aae2a0ff240c59f8d00c58e24b8e66d45e24bdbf5080f48a5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.11
|
Security for astrobeckit 0.1.4
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.