You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@petercim@shruthivis@cgreenberg@Pellarin In Figure 2A & C you show the "best scoring" human and yeast model respectively. But where are these coordinates in the repository? The README says that the output directories contain "an example of output files (*.rmf and *.dat) from sampling" but I don't see the output of the clustering anywhere - where is it? Even just the single best scoring model from the dominant cluster (presumably what you showed in the figure) would be sufficient for a minimal deposition.
The text was updated successfully, but these errors were encountered:
For the human models, output of clustering is on disk in /salilab/park1/shruthi/tfiih/tfb3_changed_humanCAK_with_apo_map/
There is a text file in that directory called best_Scoring_model.txt which shows that the single best scoring model is the last (90th) frame in rmf/models_693.0.rmf. To deposit, one would need to slice the frame in that RMF file and perhaps convert it to the latest IMP format like was done for other RMFs in this TFIIH repository.
For the yeast models I have a directory given by @petercim (/salilab/park1/shruthi/tfiih/tfiih_input/Setup_Analysis ) that shows a best_model.py. But I think this is the model before manuscript revision and I am not sure if this is the final model we published.
@petercim @shruthivis @cgreenberg @Pellarin In Figure 2A & C you show the "best scoring" human and yeast model respectively. But where are these coordinates in the repository? The README says that the
output
directories contain "an example of output files (*.rmf and *.dat) from sampling" but I don't see the output of the clustering anywhere - where is it? Even just the single best scoring model from the dominant cluster (presumably what you showed in the figure) would be sufficient for a minimal deposition.The text was updated successfully, but these errors were encountered: