40m
QIL
Cryo_Lab
CTN
SUS_Lab
TCS_Lab
OMC_Lab
CRIME_Lab
FEA
ENG_Labs
OptContFac
Mariner
WBEEShop
|
40m Log |
Not logged in |
 |
|
Sun Jul 21 02:07:04 2019, Kruthi, Update, Loss Measurement, MC2 loss map
|
Sun Jul 21 12:54:18 2019, gautam, Update, Loss Measurement, MC2 loss map
|
Sun Jul 21 17:17:03 2019, Kruthi, Update, Loss Measurement, MC2 loss map
|
Sun Jul 21 19:27:25 2019, Milind, Update, Loss Measurement, MC2 loss map
|
Mon Jul 22 12:57:35 2019, Kruthi, Update, Loss Measurement, MC2 loss map
|
|
Message ID: 14796
Entry time: Mon Jul 22 12:57:35 2019
In reply to: 14792
|
Author: |
Kruthi |
Type: |
Update |
Category: |
Loss Measurement |
Subject: |
MC2 loss map |
|
|
In my script I have used "CAM-ETMX_SNAP" only; while entering it in the elog I made a mistake, my bad!
Quote: |
I think ezca.Ezca().write() takes the string "CAM-ETMX_SNAP" as an argument and not C1:CAM-ETMX_SNAP. See this, line 47. Are you sure this is not the problem?
Quote: |
The camera server keeps throwing the error: failed to grab frames. Milind suggested that it might a problem with the ethernet cable, so I even unplugged it and connected it again; it still had the same issue. One more thing I noticed was, it does take snapshots sometimes with the terminal command caput C1:CAM-ETMX_SNAP 1, but produces a segmentation fault when ezca.Ezca().write(C1:CAM-ETMX_SNAP, 1) is used via ipython. When the terminal command also fails to take snapshots, I noticed that the SNAP button on the GigE medm screen remains on and doesn't switch back to OFF like it is supposed to.
|
|
|