Log file getting swamped with error messages #1254
Replies: 3 comments 4 replies
-
|
Could you upload your config file? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I have updated the initial post and attached our config files. |
Beta Was this translation helpful? Give feedback.
-
<PlusConfiguration version="2.9" PlusRevision="PlusApp-2.9.0.20250912-spryTrack-Telemed-Win64">
<!-- Devices for data collection -->
<DataCollection StartupDelaySec="1.0">
<DeviceSet Name="PlusServer: UKBB Atracsys spryTrack 180 and SuperSonic MACH 30 L18-5 ACQUISITION"
Description="Acquisition configuration file for tracking data from the Atracsys spryTrack 180 and video feed from the SuperSonic MACH 30 using the ultrasound probe L18-5 and the Elgato CAM LINK 4K. Broadcasting the acquired data through an OpenIGTLink."
/>
<!-- Atracsys spryTrack configuration -->
<!-- The following parameter has become internal in the latest Plus Toolkit version: -->
<!-- ActiveMarkerPairingTimeSec="15" -->
<Device
Id="TrackerDevice"
Type="AtracsysTracker"
MaxMissingFiducials="1"
MaxMeanRegistrationErrorMm="1.0"
ToolReferenceFrame="Tracker"
LocalTimeOffsetSec="0.114">
<DataSources>
<DataSource Type="Tool" Id="Probe" TrackingType="PASSIVE" GeometryFile="AtracsysTools/geometry302.ini" />
</DataSources>
<OutputChannels>
<OutputChannel Id="TrackerStream">
<DataSource Type="Tool" Id="Probe" />
</OutputChannel>
</OutputChannels>
</Device>
<!-- Ultrasound video device configuration, CaptureDeviceId=0 corresponds to the laptop's built-in webcam -->
<!-- PortUsImageOrientation may be "UN", "UF", "MF", "MN", ... -->
<!-- Added AcquisitionRate="60", BufferSize is recommended to be 5*AcquisitionRate -->
<Device Id="VideoDevice" Type="MmfVideo" AcquisitionRate="60" FrameSize="1920 1080" VideoFormat="YUY2" CaptureDeviceId="1">
<DataSources>
<DataSource
Type="Video"
Id="Video"
PortUsImageOrientation="UN"
ClipRectangleOrigin="240 120 0"
ClipRectangleSize="920 880 1"
BufferSize="300" />
</DataSources>
<OutputChannels>
<OutputChannel Id="VideoStream" VideoDataSourceId="Video" />
</OutputChannels>
</Device>
<!-- Ultrasound video and Atracsys spryTrack mixer -->
<Device Id="TrackedVideoDevice" Type="VirtualMixer">
<InputChannels>
<InputChannel Id="TrackerStream" />
<InputChannel Id="VideoStream" />
</InputChannels>
<OutputChannels>
<OutputChannel Id="TrackedVideoStream" />
</OutputChannels>
</Device>
</DataCollection>
<!-- PlusIGT configuration -->
<PlusOpenIGTLinkServer
MaxNumberOfIgtlMessagesToSend="1"
MaxTimeSpentWithProcessingMs="50"
ListeningPort="18944"
SendValidTransformsOnly="TRUE"
OutputChannelId="TrackedVideoStream" >
<DefaultClientInfo>
<MessageTypes>
<Message Type="IMAGE" />
<Message Type="TRANSFORM" />
</MessageTypes>
<TransformNames>
<Transform Name="ProbeToTracker" />
</TransformNames>
<ImageNames>
<Image Name="Image" EmbeddedTransformToFrame="Image" />
</ImageNames>
</DefaultClientInfo>
</PlusOpenIGTLinkServer>
<!-- fCal configuration -->
<fCal
StylusModelId="StylusModel"
ImageDisplayableObjectId="LiveImage"
NumberOfCalibrationImagesToAcquire="200"
NumberOfValidationImagesToAcquire="100"
NumberOfStylusCalibrationPointsToAcquire="200"
RecordingIntervalMs="100"
MaxTimeSpentWithProcessingMs="70"
ImageCoordinateFrame="Image"
ProbeCoordinateFrame="Probe"
ReferenceCoordinateFrame="Tracker"
TransducerOriginCoordinateFrame="TransducerOrigin"
TransducerOriginPixelCoordinateFrame="TransducerOriginPixel"
TemporalCalibrationDurationSec="20"
FixedChannelId="VideoStream"
FixedSourceId="Video"
MovingChannelId="TrackerStream"
MovingSourceId="ProbeToTracker"
DefaultSelectedChannelId="TrackedVideoStream"
FreeHandStartupDelaySec="5" />
</PlusConfiguration> |
Beta Was this translation helpful? Give feedback.
-
|
Have you tested to see if a config file with just the video capture can keep up? 1920x1080@60fps is a lot of data throughput |
Beta Was this translation helpful? Give feedback.
-
|
And/or does the video perform well for you during acquisition? It's just the log messages that are spamming the log? |
Beta Was this translation helpful? Give feedback.
-
|
To be fair, I tested the video capture with 30fps in a video only configuration, and changed to 60fps afterwards in the combined configuration. I will test this tomorrow in the lab, but I am somewhat confident that this should work with our HW. During the acquisition, I was watching the video and the performance seemed fine, to be honest. |
Beta Was this translation helpful? Give feedback.
-
|
So I decided to build the PlusToolkit to gain more insight/knowledge and I am currently using the following setup (CMakeCache.txt attached below)
But vkt.vcxproj fails to build with many warnings of the following type: 
3>-- Configuring incomplete, errors occurred! As a result, I run into the following problem multiple times: 14>CMake Error at src/CMakeLists.txt:3 (FIND_PACKAGE): This concerns the .vcxproj for IGSIO, OpenIGTLinkIO, and PlusLib This in turn, causes errors for the PlusApp and the PlusModelCatalog: CMake Error at CMakeLists.txt:10 (FIND_PACKAGE): Any hints on this? I first used VS 2022 and CMake 4 causing the same errors. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Dear PlusToolkit Community,
we are envisioning to perform 3D ultrasound of muscles. To this end, we have the following setup:
We have calibrated the whole setup based on pre-existing tutorials from the universities of Nantes and Basel, thank you very much Aurélie Sarcher & Fabien Stüben and Paul Ritsche!
Temporal calibration is performed with fCal and a water basin, then the pivot calibration and the probe calibration are done within 3D Slicer (RMSE of about 0.07 and 1.0 with 8 fiducial points, respectively).
After the acquisition, the goal is to perform automatic volume reconstruction, followed by manual segmentation.
But, as you might have guessed, we have a problem. We are getting swamped by error messages in the PlusToolkit Server log which look as follows:
In fact, there are so many of these messages per second, that we end up with gigantic logfiles (i.e. 2 GB in about 30min), and my gut feeling is telling me, that this is the reason for a faulty acquisition and, hence, also faulty volume reconstruction afterwards.
What I find peculiar is the fact that in the above screenshot the timestamps are almost similar, but I also have log files where the timestamps are off by seconds:
Furthermore, after starting the Plus server, 3D Slicer, and enabling an OpenIGTLinkIF (i.e. it is "On"), all is fine, but once the marker on the ultrasound probe is hidden for a brief moment (i.e. covered by hand), the errors start pouring in.
I have created a GitHub repository for our project and put the 3DSlicer sessions in, incl. a truncated Plus server log (due to the 2GB size and the repetitive nature) and our Plus server configurations:
https://github.com/Lukas-Novosad-UKBB/3D_Ultrasound_spryTrack_SuperSonic_Telemed
These are our current configuration files:
PlusToolkit_server_configurations.zip
The one used for the described acquisition and reconstruction is "PlusDeviceSet_Server_UKBB_Gaitlab_spryTrack180_SuperSonic_Mach30_L18-5_ACQUISITION.xml"
Could anybody please have a look at this and provide guidance?
If you need more details or data, please don't hesitate to let me know.
Cheers,
Lukas
Beta Was this translation helpful? Give feedback.
All reactions