-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't complete dials.symmetry
or dials.scale
jobs on some Windows machines
#190
Comments
Something to check for DUI2 |
I have a Windows 10 virtual machine so I can test and try to reproduce, I have couple of questions:
Thanks, Luiso |
We were running with the beta lactamase tutorial dataset (https://dials.github.io/documentation/tutorials/processing_in_detail_betalactamase_dui.html) As for the Czech locale, I'm not sure. I did not have time in the workshop to figure out what the common feature was between the laptops where this failed vs those where it worked. |
I've just tested this on my Windows 10 PC, where it worked okay, but what is printed to the log looked odd anyway:
I will try installing a Czech locale to see if that makes a difference. |
I managed to reproduce this by changing my Windows system locale settings to Czech. I did that in a few places, but I think the critical one is here: After that, the behaviour looks like this: DUI-symmetry-log-bug.online-video-cutter.com.mp4You can see the log gets as far as
it probably fails on the next line, which contains the
|
@luisodls Are you able to check if this is still a problem for DUI2? |
@dagewa I will check as soon as I finish what I am doing now with the I have a couple of Windows 10 virtual machines laying around, I suppose VirtualBox machines will let me reproduce, my bare metal Windows boot broke recently and I had to reformat. I will let you know how it goes. |
At the CCP4 workshop in Prague, some users with Windows laptops could not complete
dials.symmetry
ordials.scale
jobs. They would run up to a certain point at which the node would turn red and the job would appear failed.I have a suspicion it is due to special characters in the log file, in particular the first line where "CC½" is printed for example. Some Windows computers were okay, but many had this problem. It might be related to something like a Czech locale, although that is just a guess.
The text was updated successfully, but these errors were encountered: