Open spmeisburger opened 4 months ago
After rolling back to an older version of phenix (version: 1.20-4459) it worked fine.
Thanks for raising this - this is really weird! At a first glance, I don't see anything in the phenix 1.21 release notes about changes to PHIL formatting. I'm glad that fixed the issue though! I'll dig into this a little more and check back here.
Happened the same with some bash scripts I had using phenix.refine
and also with qfit3
https://github.com/ExcitedStates/qfit-3.0/issues/415.
Thanks, this is good to know! It seems like the best short-term solution is to just clarify in the documentation that phenix 1.21 is not currently supported.
@mysecondnameisdanger , do you have a working example of a refinement .eff
file for phenix 1.21? Specifically, I don't see anything in the "List of all available keywords" about a replacement for input.pdb.file_name
, input.xray_data.file_name
, or output.prefix
, all of which seem pretty essential!
https://phenix-online.org/documentation/reference/refinement.html#list-of-all-available-keywords
phenix version: 1.21-5207
Tried matchmaps for the first time on some in-house data, and it failed at the first phenix.refine step.
I re-ran with --verbose flag, and I see that phenix produces the following output:
Some of those flags do appear when I run
phenix.refine --show-defaults
, I'm not sure exactly what's wrong here. Perhaps formatting of the phil file? Or phenix version?