Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

time data #2

miguelmoreto opened this Issue Mar 27, 2019 · 4 comments


None yet
2 participants
Copy link

miguelmoreto commented Mar 27, 2019

The time data values are in the last column of the data memmap, not in the first as the example sugests.

@ldemattos ldemattos added the question label Mar 27, 2019


This comment has been minimized.

Copy link

ldemattos commented Mar 27, 2019

Hello @miguelmoreto ,

That's not what I'm finding, obviously there is some discrepancy. Check it out this small test simulation:
In [8]: time
memmap([0. , 0.01, 0.02, 0.03, 0.04, 0.05, 0.06, 0.07, 0.08, 0.09, 0.1 ,
0.11, 0.12, 0.13, 0.14, 0.15, 0.16, 0.17, 0.18, 0.19, 0.2 , 0.21,
0.22, 0.23, 0.24, 0.25, 0.26, 0.27, 0.28, 0.29, 0.3 , 0.31, 0.32,
0.33, 0.34, 0.35, 0.36, 0.37, 0.38, 0.39, 0.4 , 0.41, 0.42, 0.43,
0.44, 0.45, 0.46, 0.47, 0.48, 0.49, 0.5 , 0.51, 0.52, 0.53, 0.54,
0.55, 0.56, 0.57, 0.58, 0.59, 0.6 , 0.61, 0.62, 0.63, 0.64, 0.65,
0.66, 0.67, 0.68, 0.69, 0.7 , 0.71, 0.72, 0.73, 0.74, 0.75, 0.76,
0.77, 0.78, 0.79, 0.8 , 0.81, 0.82, 0.83, 0.84, 0.85, 0.86, 0.87,
0.88, 0.89, 0.9 , 0.91, 0.92, 0.93, 0.94, 0.95, 0.96, 0.97, 0.98,
0.99, 1. ], dtype=float32)

wideNN counter part.

Therefore, we need to level our information and simulation environment. Some question that might help:

  • Could you please share your PL4 file? (or ATP simulation file)
  • Are you adopting NEWPL2=2 in ATP startup file? (PISA PL4 format)
  • Did you change some index value when converting from python2 to 3?

Thanks for the contribution!


This comment has been minimized.

Copy link

ldemattos commented Mar 27, 2019

Hello, @miguelmoreto !

I've tested my code version over the file simulacao.pl4, and I could confirm the issue that you are commenting.

However, opening your pl4 file with hexdump I could verify that you file is slightly different than mine.



Mind that your data skips from row 0000130 to 00000160 when it changes from variable description to actual data. Moreover, in your file seems to exists a row of zeroes before the actual data in row 00000160, which doesn't happens in mine. Also consider that your variable 1X800A-TERRA (node voltage) is not zero at t=0.0, as it may suggest reading you binary file with the structure that I discover from my pl4 files.

Conversely, in my pl4 file we don't see this row bump. This may suggest that your pl4 format is different from the one that I'm using. In doing so, please check your ATP startup file, as described above. You can check my binary data file here.. Would be interesting also to check what atp solver version we are using, they may differ.

Thanks for your time.


This comment has been minimized.

Copy link

miguelmoreto commented Mar 28, 2019

Hello @ldemattos,

I had noticed these rows of zeros before, but I had though that this was my actual simulation data. I had other PL4 file where the number of zeros is different. As a result, the time vector is in another position among the other data. My STARTUP file contains the configuration NEWPL4 = 2. It seems that the number of zeros is related with the number of channels. The more channels the more zeros are in the file, strange....
I don't know the version of the solver. Do you know how to check the version? The file name is tpbig.exe.


This comment has been minimized.

Copy link

ldemattos commented Apr 10, 2019

Hello @miguelmoreto ,

Sorry to taking so long to reply. Things are pretty wild here. I don't know how to check which solver version the case has been simulated. I just know the version by checking it when downloading from ATP solver, and then marking it somehow. I'll e-mail the ATP mailing list to see if there is some way to do this.

So we already know that this issue doesn't come from NEWPL4 flag. I will strike through it above. Thanks.

I did further comparison on our binary files, besides the fields that we already know, only the fields painted as green in the figure below differs between our files. In doing so, I believe if there is some clue about these additional rows of zeroes it must be given in these fields.
The fields painted as red are filled equally.

We could as well compare both ATP's startup file and simulation data case (especially the misc data cards. I would like to know the root of those additional zeroes.

I did thought a way to strip out those unwanted zeroes rows. As we know the complete size of PL4 file (PL4 SIZE), the number of variables, the header length and so on, we can calculate how much of undesired data is in in between the actual simulation results and the variable description. Hence, we can skip them. I'll write a proposal and commit it. Please test it with your data.

Best regards,

ldemattos added a commit that referenced this issue Apr 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.