Build XASObject in GUI via read_from_input_information
2 unresolved threads
2 unresolved threads
Fix #88 (closed)
Thanks to previous refactorings, I was able to completely replace the custom loading code in XASObjectDialog
by a simple call to read_from_input_information
.
The building of XASObject is now consistent between the GUI and the Ewoks task: both use read_from_input_information
. The only difference is that the GUI generates its own input_information
by reading the QtWidget values while the Ewoks task takes it as input (if I dare say).
Edited by Loic Huder
Merge request reports
Activity
added 3 commits
-
f9db7e5a...81e026bb - 2 commits from branch
main
- 48743e0e - Build XASObject in GUI via read_from_input_information
-
f9db7e5a...81e026bb - 2 commits from branch
added 1 commit
- 6b19fc68 - Build XASObject in GUI via read_from_input_information
added 1 commit
- 98b46bbe - Build XASObject in GUI via read_from_input_information
7 from est.core.io import read_from_url 8 from est.core.io import read_from_ascii 8 from est.core.io import read_from_input_information 9 9 from est.io.information import InputInformation 10 10 from est.io.utils.ascii import build_ascii_data_url 11 11 from .ascii import XASObjectFromAscii 12 12 from .hdf5 import XASObjectFromH5 13 13 14 14 15 def _check_url(url_path, name): 16 if isinstance(url_path, DataUrl): 17 url = url_path 18 else: 19 url = DataUrl(path=url_path) 20 if not url.is_valid(): 21 raise ValueError(f"{name} url is invalid. Does the file / path still exists ?") requested review from @payno
239 208 ) 240 209 241 210 def getMonitorUrl(self): 211 # TODO" UNUSED changed this line in version 8 of the diff
mentioned in commit f4b8ea69
mentioned in merge request !148 (merged)
Please register or sign in to reply