This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
processing:remove-used-gve [2019/06/04 14:54] matthias |
processing:remove-used-gve [2020/11/10 08:56] (current) smerkel |
||
---|---|---|---|
Line 2: | Line 2: | ||
===== Description ===== | ===== Description ===== | ||
- | |||
- | The script ''timelessRemoveUsedGVE.py'' is part of the [[software:timelesstools|TIMEleSS tools]]. It should be combined with [[software:grainspotter|GrainSpotter]] and [[software:grainspottermerge|GrainSpotterMerge]]. | ||
In the [[processing:indexing_with_grainspotter|process of grain indexing]] (usually done with [[software:grainspotter|GrainSpotter]]), you won't index all grains in the first try. Usually, one has to perform several indexing runs. To make life easier (and to cut down calculation time), this script removes all G-vectors which were used already in the previous run. Then you can perform another run with the reduced G-vector file. After that, this process can be repeated until GrainSpotter doesn't index anything anymore. | In the [[processing:indexing_with_grainspotter|process of grain indexing]] (usually done with [[software:grainspotter|GrainSpotter]]), you won't index all grains in the first try. Usually, one has to perform several indexing runs. To make life easier (and to cut down calculation time), this script removes all G-vectors which were used already in the previous run. Then you can perform another run with the reduced G-vector file. After that, this process can be repeated until GrainSpotter doesn't index anything anymore. | ||
- | The downside is that one has to modify the //.ini// file and the input of ''timelessRemoveUsedGVE.py'' before every new run (we are currently working on a script which avoids this). However, it is worth it: Experience says that you can increase the number of indexed grains easily by more than 30 %, simply by repeating the GrainSpotter algorithm. Usually, 5-6 repetitions are enough before GrainSpotter does not find any new grains anymore. | + | The downside is that one has to modify the //.ini// file and the input of this tool before every new run (we are currently working on a script which avoids this). However, it is worth it: Experience says that you can increase the number of indexed grains easily by more than 30 %, simply by repeating the GrainSpotter algorithm. Usually, 5-6 repetitions are enough before GrainSpotter does not find any new grains anymore. |
+ | |||
+ | For historical reasons, there are two competing TIMEleSS tools for this task, ''timelessRemoveUsedGVE.py'' and ''timelessClearGVEGrains''. ''timelessClearGVEGrains'' has been updated recently and has more options. | ||
+ | |||
+ | ==== timelessClearGVEGrains ==== | ||
+ | |||
+ | <code> | ||
+ | timelessClearGVEGrains -h | ||
+ | usage: timelessClearGVEGrains GSFile oldGVE.gve newGVE.gve | ||
+ | |||
+ | Creates a new list of g-vectors, removing g-vectors which have already been | ||
+ | assigned to grains by GrainSpotter This is part of the TIMEleSS project | ||
+ | http://timeless.texture.rocks | ||
+ | |||
+ | positional arguments: | ||
+ | gsfile Name of GrainSpotter output file (required) | ||
+ | oldGVE G-vector file used for indexing (required) | ||
+ | newGVE Name of G-vector file to be created (required) | ||
+ | |||
+ | optional arguments: | ||
+ | -h, --help show this help message and exit | ||
+ | -v VERBOSE, --verbose VERBOSE | ||
+ | Write out more details about what it does. Default is | ||
+ | Default is False | ||
+ | -s SKIPBOGUS, --skipbogus SKIPBOGUS | ||
+ | Skip bogus grains in GrainSpotter output. Default is | ||
+ | Default is False | ||
+ | |||
+ | </code> | ||
+ | |||
+ | ==== timelessRemoveUsedGVE.py ==== | ||
+ | |||
+ | The script ''timelessRemoveUsedGVE.py'' is part of the [[software:timelesstools|TIMEleSS tools]]. It should be combined with [[software:grainspotter|GrainSpotter]] and [[processing:grainspotter-merge|GrainSpotterMerge]]. | ||
<code> | <code> | ||
Line 60: | Line 90: | ||
==== Merging the output ==== | ==== Merging the output ==== | ||
- | Use | + | Use [[processing:grainspotter-merge|GrainSpotterMerge]] to merge the produced //.log// files. |