Problems: Difference between revisions

Problems (view source)

No change in size , 10 March 2022

no edit summary

2,652

edits

@@ Line 57: / Line 57: @@
      bash: export KMP_INIT_AT_FORK=FALSE
      tcsh: setenv KMP_INIT_AT_FORK FALSE
-=== frame numbers beyond 999999 ===
-If the number of question marks "?" in NAME_TEMPLATE_OF_DATA_FRAMES is larger than 6, to allow for e.g.
- DATA_RANGE= 1000001 10001000
-then IDXREF cannot properly read SPOT.XDS written by COLSPOT, and stops with
-  !!! ERROR !!! CANNOT READ SPOT.XDS
-This happens when the filenames of the frames have digits before the actual number, as in myframe1000001.cbf .
-The workaround is to specify e.g.
- NAME_TEMPLATE_OF_DATA_FRAMES=myframe100????.cbf
- DATA_RANGE=1 1000
-(Problem reported by Pedro Dinis)
 === ASSERT VIOLATION ===
@@ Line 265: / Line 252: @@
 A final possibility: your crystal may really be triclinic - hopefully you collected 180° of data, or even a bit more than that.
+=== frame numbers beyond 999999 ===
+If the number of question marks "?" in NAME_TEMPLATE_OF_DATA_FRAMES is larger than 6, to allow for e.g.
+ DATA_RANGE= 1000001 10001000
+then IDXREF cannot properly read SPOT.XDS written by COLSPOT, and stops with
+  !!! ERROR !!! CANNOT READ SPOT.XDS
+This happens when the filenames of the frames have digits before the actual number, as in myframe1000001.cbf .
+The workaround is to specify e.g.
+ NAME_TEMPLATE_OF_DATA_FRAMES=myframe100????.cbf
+ DATA_RANGE=1 1000
+(Problem reported by Pedro Dinis)
 == Integration failure ==