Use .content rather than .project_hdf5

[pmrv]

This allows .output to work with Sphinx jobs that use strange output format.

[jan-janssen]

This allows .output to work with Sphinx jobs that use strange output format.

Does this break LAMMPS and VASP?

[coveralls]

Pull Request Test Coverage Report for Build 10143456330

Details

• 36 of 57 (63.16%) changed or added relevant lines in 2 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.01%) to 70.921%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
pyiron_atomistics/atomistics/job/atomistic.py	13	20	65.0%
pyiron_atomistics/table/funct.py	23	37	62.16%
<!--	Total:	36	57	63.16%	-->

Files with Coverage Reduction	New Missed Lines	%
pyiron_atomistics/table/funct.py	1	61.15%
<!--	Total:	1		-->

Totals
Change from base Build 10106288863:	0.01%
Covered Lines:	10707
Relevant Lines:	15097

---

💛 - Coveralls

[pmrv]

This allows .output to work with Sphinx jobs that use strange output format.

Does this break LAMMPS and VASP?

The only difference between .content and .project_hdf5 is that the former tries to to_object() any DataContainers it finds, but otherwise returns the same, so I can't see why it would make problems. Technically .content raises KeyErrors instead of ValueErrors which is what caused the test failures on the weekend, but since .output anyway always silenced those to None, no outside code should depend on this.

@samwaseda Can you add a test case for #1508?

[jan-janssen]

@pmrv Should we adjust the pyiron table to also use content rather than output ?

[pmrv]

@pmrv Should we adjust the pyiron table to also use content rather than output ?

You mean the predefined datamining functions? Yes, that would make sense.

[jan-janssen]

@samwaseda Can you confirm this is working for SPHInx? I would like to release a new pyiron_atomistics version today.