DSR
The program DSR consists of a text database with fragments of molecules and the DSR program. It acts as a preprocessor for SHELXL .res files. The user inserts a special command in the SHELXL .res file and the DSR program reads this information to put a molecule or fragment with the desired atoms on the position of the target atoms or q-peaks in the unit cell. Bond restraints can be either applied from the database to the molecule or automatically generated.
I apologize for the messy code. This was my first bigger project...
You have either a command line version:
C:\Users\daniel>dsr
----------------------------------------------------- D S R - v211 -------------------------------------
Disordered Structure Refinement (DSR)
Example DSR .res file command line:
REM DSR PUT/REPLACE "Fragment" WITH C1 C2 C3 ON Q1 Q2 Q3 PART 1 OCC -21 =
RESI DFIX
---------------------------------------------------------------------------------------------------------
PUT: Just put the fragment source atoms here.
REPLACE: Replace atoms of PART 0 in 1.3 A distance around target atoms.
---------------------------------------------------------------------------------------------------------
optional arguments:
-h, --help show this help message and exit
-r "res file" ["res file" ...]
res file with DSR command
-re "res file" ["res file" ...]
res file with DSR command (write restraints to external file)
-e "fragment" export fragment as .res/.png file
-c "fragment" export fragment to clipboard
-t inverts the current fragment
-i "tgz file" import a fragment from GRADE (needs .tgz file)
-l list names of all database entries
-s "string" search the database for a name
-g keep group rigid (no restraints)
-u Update DSR to the most current version
-n do not refine after fragment transfer
Or a graphical user interface in ShelXle:
Metadata
Release files for dsr-shelx 237
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 |
|---|---|---|---|---|
| dsr_shelx-237.tar.gz | 1.3 MB | Without provenance | Details for dsr_shelx-237.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dsr_shelx-237-py3-none-any.whl | Python 3 | none | any | Details for dsr_shelx-237-py3-none-any.whl |
Total release size: 2.8 MB
Release files / dsr_shelx-237.tar.gz
| Download URL | dsr_shelx-237.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6a9cc8ae62ff20f9785a024eb0f50fcb6fa453f1a1afb76723d0ca80ec321859
|
|
BLAKE2b-256 checksum How to use checksums |
e47434d5d47ade3c48e78d179f57182d1fe28904f3ee545ef9e6fbfc30f1a0b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.0
|
Release files / dsr_shelx-237-py3-none-any.whl
| Download URL | dsr_shelx-237-py3-none-any.whl |
|---|---|
| Size | 1.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b93262c75f2a5049c048e2bd3302e8f43c7ccb84e91b53bda5a76177e6a9d4e1
|
|
BLAKE2b-256 checksum How to use checksums |
70640bba8d6d4c080ffc5bd1118f590d36bd40c56963e40cef3608496d81dcc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.0
|
Security for dsr-shelx 237
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.