Skip to content

Issue on generation of additional empty MAT file #14

Description

@shbang91

Hello,

Thank you for maintaining this nice repo!

While doing my project, I encountered an issue with having an additional empty MAT file when saving data using Matlogger. The following statements are a high-level overview of the software architecture that I'm using.

I have a class A that has a Matlogger instance called logger_ (which is initialized with logger_ = XBot::MatLogger2::MakeLogger("/tmp/data")). Let's suppose that I create an instance of class A as A *a = new A(); and I repeatedly destruct delete a; and construct a = new A(); inside of a while loop which is always running in the background.
After deleting a once, killing the process (the while loop), and checking the data.mat, I always find there are two data.mat file in which one of them is empty.

My understanding from looking at the document of Matlogger is that once I create and delete class instance a, I should have just one data.mat file because logger_ dumps the data when it is destructed (which is automatically destructed when I delete a).

If you have any idea or guidance that could resolve this issue, I would really appreciate it.

Thank you,

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions