Skip to content

Bad file format to save the trajectory of the double well potential #4

Description

@dprada

We are currently saving the trajectory in a UTF-8 encoded text file with four columns: time, $x$, $y$, and $z$. Not a very wise choice.

The size of trajectory with 15 microseconds saved every 10 picoseconds is ~118M. Not big if we work locally with this file on our machine. But big enough to be uploaded to this repository (There is a 100M limit per file). So... we need to work with a better file format.

Activity

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingenhancementNew feature or request

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions