Using riCOM

[GearoidM]

Hello,

I am looking for additional guidance on using the riCOM package.

I recently tried to use riCOM on a JEOL microscope with Digiscan controlled scanning. I installed the software (precompiled executable) on the MerlinEM's host PC, downloaded the additional merlin_interface.py file and placed it in the folder containing the riCOM executable.

I am not sure how to use riCOM to collect any data. The MerlinEM scan software is open, the relevant parameters in the riCOM, MerlinEM scan and GMS (for Digiscan) software match. RiCOM says "connected", so I assume that riCOM and Merlin are communicating over TCP/IP. Starting an acquisition does not seem to do anything. To elaborate, a window opens and closes in under a second.

I expected that the camera status would update to armed when clicking on the start acquisition. After which, I would start scanning with Digiscan, sending pixel triggers to Merlin. Then riCOM would use the data streamed over TCP/IP to generate an integrated COM image in real time.

Could you please advise me on how to get riCOM working? Should I use the MerlinEM PC or connect to a second PC?

Best wishes.

Gearóid.

[Chu-Ping]

Hi Gearóid,
First of all, thanks for using RiCOM.
Your description about the workflow seems to be correct, and I have not seen problems with windows poping up and then disappear, so I am afraid that we need more details. Here's how you can help us.

1. The window you're refering to, does it belong to the RiCOM program, or it is something else?
2. Do you run merlin in headless mode? and what are the settings (bit depth, dwell time, ...)?
3. During acquisition, what is shown on Merlin's software?
4. Could you try record the data first with Merlin's software, and then use RiCOM to process the file?

p.s. In our experience, using MerlinPC should suffice.

[GearoidM]

Dear Chu-Ping,

Thanks for getting back to me.

I tested riCOM when I visited a lab a couple months ago. Unfortunately, I do not have access to the microscope anymore, so I cannot get some of the details requested here.

1. It's hard to tell where the window was coming from. I could not interact with it as it closed under a second after opening. I am guessing it came from riCOM.
2. Merlin was not running in headless mode. I tested in both continuous 12-bit and 6-bit mode, with the fastest possible frame time (650 us for 12-bit, I think. Digiscan dwell time was set smaller than Merlin's frame time ), 128x128 scanning on both riCOM and Digiscan (and Merlin host software), skip img and row matched Merlin software (I forgot the exact values).
3. As far as I remember, Merlin software did not change. What do you expect it to show?
4. I could potentially do this when I visit another lab.

Thanks again

Gearóid