Issue with Output File.

[StanV000]

Hi,

I've been testing the videoconferencing application and encountered an issue.

Experiment runs smoothly, however once it completes, the output file that I get "out.csv" remains empty. Containing only the header row. When I ran the experiment a second time, the output file generated incorrect data.

Further look I went to /celestial/out used nano into gst-tracker.out, where I found an issue indicating that the path is blocked. I as well do not have docker installed. I am unsure what the problem might be since the quickstart application ran without problems. Any insight would be greatly appreciated.

[pfandzelter]

Hi, thanks for opening this. It seems like there definitely are some issues with the use of the Celestial API in our code. I fixed these in the tp/fix-tracker branch. Could you please check if this resolves issues or if others pop up?

[StanV000]

Hello,

Thank you for getting back to me. I have done as you asked, and I’m currently getting these problems along with an update of the out.csv file.

[pfandzelter]

Peculiar... It seems as if the issue is just that ground stations 2 and 3 are not reachable on their HTTP port 8000? Not sure what could be causing this. Is the output of ground station 1 as expected?

Unfortunately I have no way of testing this myself at the moment

[StanV000]

Hi,

Yes I ran it a few times, now I have gs1, gst2 running however but not gst3. The same problem of it not establishing a connection. I have some more insight that could help.

Before updating to tp/fix-tracker I used "videoconferencing-test.toml" and I had gst-1 , gst-2 and gst-3 all working and connecting to to the tracker, however absolutely no data was being generated, I tested this out now again using the updated tracker, I have gs1,gst2 working but gst3 not. With the same data being generated as before.

Below is the image for gst-1 that is identical for gst-2 but however gst-3 is still "Waiting for a target address".

Could this issue arise from the fact that it was built wrong?, I didn't build it using docker, however I can do that and see if it'll work. I as well use the default celestial client that we got and built the server(maybe one of them could be wrong?).

[StanV000]

I was messing with it a bit more, I used videoconference-satellite.toml and I put the bounding box from videoconference-test.toml, I changed tracker.img to tracker-alt.img.

After doing that I got.

I then messed around again and just decided to use the default videoconference-test.toml instead without altering anything else. At one point they run fine for a few updates , I checked the output of gst-1-2-3 and they're connecting fine but then they just all 3 stop working. Following below are the images of the tracker.

My apologies for the hassle. I am not sure if it is an issue on my side.

[pfandzelter]

Sorry for the late response, and thank you for continuing to investigate! I will have to try this out myself to narrow down what could be causing this, unfortunately I will not be able to do so in the coming days. But I have this on my backlog!