「view this page in B3 βῆτα server」

Revisions №60024

branch: master 「№60024」
Commited by: Andrew Leaver-Fay
GitHub commit link: 「b92b82cd8640aa73」 「№2919」
Difference from previous tested commit:  code diff
Commit date: 2018-02-07 08:18:26

Merge pull request #2919 from RosettaCommons/aleaverfay/fix_features_integration_test fix currently-failing features integration test Putting the output name for the job into the Pose. Perhaps this is the appropriate way to deliver the job name to a Mover instead of through parse_my_tag. There seems to be a good amount of code already for grabbing the JOBDIST_OUTPUT_TAG scattered through the code base. In my aleaverfay/revive_resource_manager branch, I had started down a path that would transmit currently-running-job information to Movers via parse_my_tag by putting strings into the DataMap. This would require, however, re-parsing a Mover for each job, and that has its own disadvantages. Putting the data into the Pose, however, seems like a fine way to get this done. I'm thinking this stopgap fix will migrate downward into the StandardJobQueen's pose_for_job() method.