use project_hdf5 in pacemaker instead of job directly

pyiron · Feb 28, 2024 · f8de4e3 · f8de4e3
1 parent fb91765
commit f8de4e3
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/pyiron_potentialfit/pacemaker/job.py b/pyiron_potentialfit/pacemaker/job.py
@@ -373,7 +373,7 @@ def collect_output(self):
             predicted_data_fs.to_hdf(hdf=hdf5_output, group_name="predicted_data")
 
     def get_lammps_potential(self):
-        elements_name = self["output/potential/elements_name"]
+        elements_name = self.project_hdf5["output/potential/elements_name"]
         elem = " ".join(elements_name)
         pot_file_name = self.get_final_potential_filename_ace()
         pot_dict = {
@@ -428,10 +428,10 @@ def add_job_to_fitting(self, job_id, *args, **kwargs):
         self._train_job_id_list.append(job_id)
 
     def _get_training_data(self) -> TrainingStorage:
-        return self["output/training_data"].to_object()
+        return self.project_hdf5["output/training_data"].to_object()
 
     def _get_predicted_data(self) -> FlattenedStorage:
-        return self["output/predicted_data"].to_object()
+        return self.project_hdf5["output/predicted_data"].to_object()
 
     # copied/adapted from mlip.py
     def create_training_dataframe(