Dear colleagues, we would like to invite you for a meeting about data reduction. This topic has been discussed since years. However, the new detectors which have recently been installed are seriously challenging our IT infrastructure. To cope with this situation our colleagues from the computer center are very much interested to understand the processes involved and to learn about the requirements from the experiments. This information would help them to optimize their services, like data storage, data and meta data management, data processing and ongoing developments of ASAPO. Another purpose of this meeting is to raise the general awareness for this topic. It should stimulate new activities in this area and we should also understand where progress can be made and what resources are necessary to make substantial improvements. In addition we should see whether the possibility exists to join forces creating synergy. We are also interested to hear which experiments have fundamental problems to reduce their data. We encourage you to present wishlists, apply brainstorming. Do not be concerned with technical details at this early stage.
Options:
Issues: Python2 and Qt4 not really supported under Debian-11.
Tests have started.
When the Macroserver starts, all Python files in the MacroPath directories are imported. This way, Macros are made available. If there are other Python files in the MacroPath, they are also imported.
Two rules:
Bad code:
#!/usr/bin/env python # # BAD: DoSomething() is executed during imports # def DoSomething(): print( "Hello world") return DoSomething()
Correct code:
#!/usr/bin/env python # # Good: DoSomething() is NOT executed during imports # def DoSomething(): print( "Hello world") return if __name__ == "__main__": DoSomething()
Note 1: SardanaMacroTester.py finds naming conflicts for Macros and it finds scripts
not containing 'macro' and not containing __name__
.
Note 2: Sometimes scientists collect Macros for a user group in a module, say mod1.py. The next user group might require small changes. If mod1.py is copied to mod2.py (which is then changed) the naming conflicts arise. Solution: rename mod1.py to e.g. mod1.py.DateTimeUniKiel.
Actions: step == 0 will no longer cause a move, RecentWrites extended, new server at P23, testing.
...
, testAlive=True) fixed: should launch a pyspMonitor, done.
Triggered an upgrade of hasyutils.
Triggered an update of pyspectra.