Tuesday, 21 July 2015
With ongoing sf.net outage...
We are looking to move xia2 to github, so for those of you who pull xia2 from subversion this will be a significant change. Also the "home" of xia2 will change as well - though this blog will remain, so watch this space...
Sunday, 19 July 2015
sf.net outage
You may have noticed that xia2 things are not working - the svn is dead; the nightly builds are empty etc. - this is because the hosting service I use (sourceforge.net) is currently broken and has been for getting on for four days. They're in the process of restoring services (web now back, but svn is not) and normal service should resume soon.
See here for more details.
See here for more details.
Thursday, 16 July 2015
Windows...
Does anyone use xia2 / DIALS on MS Windows? Would you want to? Was pointed out to me that the changes referred to in the previous post would not work gracefully on MS Windows due to the c:\ type file paths... this should probably be fixed anyhow. Shout if you have an opinion.
New logs in the LogFiles directory; more image= options
If you look in LogFiles and you use xia2 -dials you will find some new stuff in there:
Graemes-MacBook-Pro-2:image_range graeme$ ls LogFiles/
AUTOMATIC_DEFAULT_NATIVE_truncate.log AUTOMATIC_DEFAULT_pointless.log
AUTOMATIC_DEFAULT_aimless.log SWEEP1_INDEX.log
AUTOMATIC_DEFAULT_aimless_xml.xml SWEEP1_LATTICE.log
This now includes the indexing log file and the lattice determination one; these can be useful to see how xia2 made it's decisions.
Also, if you want to combine some data from several sweeps, but only use limited image ranges, you can with:
xia2 unify_setting=true -atom Ti -small_molecule -dials image=/Users/graeme/data/i04-KTP/1/KTP_1_0001.cbf:1:100 image=/Users/graeme/data/i04-KTP/2/KTP_2_0001.cbf:1:100
so this will use the first 100 images of two sweeps and will make this xinfo file:
BEGIN PROJECT AUTOMATIC
BEGIN CRYSTAL DEFAULT
BEGIN HA_INFO
ATOM ti
!NUMBER_PER_MONOMER N
!NUMBER_TOTAL M
END HA_INFO
BEGIN WAVELENGTH SAD
WAVELENGTH 0.729320
END WAVELENGTH SAD
BEGIN SWEEP SWEEP1
WAVELENGTH SAD
DIRECTORY /Users/graeme/data/i04-KTP/1
IMAGE KTP_1_0001.cbf
START_END 1 100
END SWEEP SWEEP1
BEGIN SWEEP SWEEP2
WAVELENGTH SAD
DIRECTORY /Users/graeme/data/i04-KTP/2
IMAGE KTP_2_0001.cbf
START_END 1 100
END SWEEP SWEEP2
END CRYSTAL DEFAULT
END PROJECT AUTOMATIC
Word of warning though that this will currently (as of noon today) only cope with one subset per sweep; should be easy enough to add multiple image ranges for this though need to think what syntax to use... as always feedback welcome to xia2.support@gmail.com; to get this you will need to pull a new DIALS nightly build later today or tomorrow.
Monday, 13 July 2015
More output: how much is too much?
Request of additional output from xia2 e.g. in the indexing table:
adding the R.M.S.D., metric penalty etc. from for example dials.index. This will however make for more "junk" in the output and will also depend on the package being run underneath. Also requested was number of spots indexed vs. total number of spots. This will make for more information in the output which could make it cluttered and will also have the potential to "break" other software which uses this.
Thoughts anyone?
------------------- Autoindexing SWEEP1 --------------------
All possible indexing solutions:
oP 6.39 10.59 12.80 90.00 90.00 90.00
mP 6.39 12.80 10.59 90.00 89.99 90.00
aP 6.39 10.59 12.80 90.00 90.00 89.99
Indexing solution:
oP 6.39 10.59 12.80 90.00 90.00 90.00
adding the R.M.S.D., metric penalty etc. from for example dials.index. This will however make for more "junk" in the output and will also depend on the package being run underneath. Also requested was number of spots indexed vs. total number of spots. This will make for more information in the output which could make it cluttered and will also have the potential to "break" other software which uses this.
Thoughts anyone?
Subscribe to:
Posts (Atom)