Update README.md
This commit is contained in:
@ -43,7 +43,7 @@ In case of installation from source, so different location of the code and conda
|
|||||||
## Configuration files<a name="config"></a>
|
## Configuration files<a name="config"></a>
|
||||||
|
|
||||||
### BEAM_ENERGY.txt
|
### BEAM_ENERGY.txt
|
||||||
This file should contain a beam energy values (in eV). There must be one line with the default values and (optionally) it's possible to define beam energy values, different from defaults for specific runs(scans). Example:
|
This file should contain a beam energy values (in eV). There must be one line with the default value and it's possible to define beam energy values, different from defaults for specific runs(scans). Example:
|
||||||
> $ cat BEAM_ENERGY.txt
|
> $ cat BEAM_ENERGY.txt
|
||||||
>
|
>
|
||||||
> DEFAULT 11330.0
|
> DEFAULT 11330.0
|
||||||
@ -75,7 +75,7 @@ this file contains indexing parameters used by crystfel.
|
|||||||
|
|
||||||
**HINT** - in case several proteins are used during expertiment, it's possible to define different indexing parameters for each of them: in case run_index.<cell_name>.sh file is present - indexing parameters from that file will be used to process <cell_name> protein sample, if not present(default) - run_index.sh parameters are used
|
**HINT** - in case several proteins are used during expertiment, it's possible to define different indexing parameters for each of them: in case run_index.<cell_name>.sh file is present - indexing parameters from that file will be used to process <cell_name> protein sample, if not present(default) - run_index.sh parameters are used
|
||||||
|
|
||||||
## Google Authentication (optional)<a name="google-api"></a>
|
## Google Authentication<a name="google-api"></a>
|
||||||
|
|
||||||
ap can fill automatically google spreadsheet with different information. This is done using google-api and one need to have api-keys created and allowed for the corresponding spreadsheet (logbook). To create keys, few steps needs to be done first:
|
ap can fill automatically google spreadsheet with different information. This is done using google-api and one need to have api-keys created and allowed for the corresponding spreadsheet (logbook). To create keys, few steps needs to be done first:
|
||||||
- [enable API access for a project](https://docs.gspread.org/en/v5.10.0/oauth2.html#enable-api-access-for-a-project)
|
- [enable API access for a project](https://docs.gspread.org/en/v5.10.0/oauth2.html#enable-api-access-for-a-project)
|
||||||
@ -119,7 +119,6 @@ this file contains indexing parameters used by crystfel.
|
|||||||
|
|
||||||
runs with the <cell_name>=lyso will be indexed using lyso.cell file, while for the <cell_name>=chim - indexing will be done twice, using chim.cell and chim.cell_alternative files (and results of both indexing will be filled in logbook)
|
runs with the <cell_name>=lyso will be indexed using lyso.cell file, while for the <cell_name>=chim - indexing will be done twice, using chim.cell and chim.cell_alternative files (and results of both indexing will be filled in logbook)
|
||||||
|
|
||||||
* (optional, if filling is requested)
|
|
||||||
|
|
||||||
* create (an empty) google spreadsheet
|
* create (an empty) google spreadsheet
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user