Skip to content
This repository has been archived by the owner on Mar 25, 2024. It is now read-only.

packet-processor crashes if triggers are out of order #11

Open
BenMoon opened this issue May 29, 2021 · 1 comment
Open

packet-processor crashes if triggers are out of order #11

BenMoon opened this issue May 29, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@BenMoon
Copy link
Contributor

BenMoon commented May 29, 2021

Traceback (most recent call last):
  File "/home/bl1user/.conda/envs/TPXOct20-ion/lib/python3.7/logging/__init__.py", line 1025, in emit
    msg = self.format(record)
  File "/home/bl1user/.conda/envs/TPXOct20-ion/lib/python3.7/logging/__init__.py", line 869, in format
    return fmt.format(record)
  File "/home/bl1user/.conda/envs/TPXOct20-ion/lib/python3.7/logging/__init__.py", line 608, in format
    record.message = record.getMessage()
  File "/home/bl1user/.conda/envs/TPXOct20-ion/lib/python3.7/logging/__init__.py", line 369, in getMessage
    msg = msg % self.args
TypeError: not all arguments converted during string formatting
Call stack:
  File "/home/bl1user/.conda/envs/TPXOct20-ion/lib/python3.7/threading.py", line 890, in _bootstrap
    self._bootstrap_inner()
  File "/home/bl1user/.conda/envs/TPXOct20-ion/lib/python3.7/threading.py", line 926, in _bootstrap_inner
    self.run()
  File "/home/bl1user/.conda/envs/TPXOct20-ion/lib/python3.7/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "/home/bl1user/TPXOct20-ion/pymepix/pymepix/core/log.py", line 70, in _logging_thread
    _log.log(log_level, message, *args, **kwargs)
Message: 'Exception has occured {} due to '
Arguments: ('bins must be monotonically increasing or decreasing',)
2021-05-29 17:51:52,009 - pymepix.PacketProcessor - ERROR - Writing output TOA [2047.17944828 2047.17944976 2047.17945109 ... 2066.75999535 2066.75999797
 2066.76000011]
2021-05-29 17:51:52,009 - pymepix.PacketProcessor - ERROR - Writing triggers [2046.55848835 2073.50204469 2066.65998975 2066.7600005 ]
2021-05-29 17:51:52,009 - pymepix.PacketProcessor - ERROR - Flushing triggers!!!
--- Logging error ---
Traceback (most recent call last):
  File "/home/bl1user/.conda/envs/TPXOct20-ion/lib/python3.7/logging/__init__.py", line 1025, in emit
    msg = self.format(record)
  File "/home/bl1user/.conda/envs/TPXOct20-ion/lib/python3.7/logging/__init__.py", line 869, in format
    return fmt.format(record)
  File "/home/bl1user/.conda/envs/TPXOct20-ion/lib/python3.7/logging/__init__.py", line 608, in format
    record.message = record.getMessage()
  File "/home/bl1user/.conda/envs/TPXOct20-ion/lib/python3.7/logging/__init__.py", line 369, in getMessage
    msg = msg % self.args
TypeError: not all arguments converted during string formatting
Call stack:
  File "/home/bl1user/.conda/envs/TPXOct20-ion/lib/python3.7/threading.py", line 890, in _bootstrap
    self._bootstrap_inner()
  File "/home/bl1user/.conda/envs/TPXOct20-ion/lib/python3.7/threading.py", line 926, in _bootstrap_inner
    self.run()
  File "/home/bl1user/.conda/envs/TPXOct20-ion/lib/python3.7/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "/home/bl1user/TPXOct20-ion/pymepix/pymepix/core/log.py", line 70, in _logging_thread
    _log.log(log_level, message, *args, **kwargs)
Message: 'Exception has occured {} due to '
Arguments: ('bins must be monotonically increasing or decreasing',)
2021-05-29 17:55:05,786 - pymepix.PacketProcessor - ERROR - Writing output TOA [2046.45847847 2046.45847848 2046.45847848 ... 2089.85929619 2089.85929793
 2089.85930033]
2021-05-29 17:55:05,786 - pymepix.PacketProcessor - ERROR - Writing triggers [2046.4584776  2066.96002198 2067.06003273 2067.16004347 2094.10359981
 2089.75929128 2089.85930203]
2021-05-29 17:55:05,786 - pymepix.PacketProcessor - ERROR - Flushing triggers!!!

I've see this error before in very old data. It may be hardware related and it is not really preproducable.

@BenMoon BenMoon added the bug Something isn't working label May 29, 2021
@jokuha
Copy link
Member

jokuha commented Jun 1, 2021

This report looks as if it needs a bit more context and descriptive details to be reasonable and understandable down the line when one might get back to it...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants