JSON structure could be a lot more compact

[Vaguery]

Disregarding key strings, could we please restructure the JSON output so that it doesn't say the generation for every individual? Something like this comes to mind:

{
  {
    "generation" : 1,
    "individuals" :
      [
        {«individual 1 here»},
        {«individual 2 here»},
        ...
      ]
  },
  {
    "generation" : 2,
    ...
  },
  ...
}

[thelmuth]

This applies to all your JSON issues: As far as I know, no one is using the JSON printing, nor has for many years. It was hastily added long ago, and I just threw things together piecemeal. Feel free to change it entirely or delete it or do whatever you like -- the current implementation is at best buggy and poorly written.

[Vaguery]

I will totally use the JSON printing, since CSV makes the baby Interoperability cry.

[Vaguery]

Would it be a problem if I changed things so that the JSON output is stored in a more communicative location, as well? I'm thinking of a "results" or "reports" subdirectory, whatever makes more sense, and named with the actual run ID rather than generic filename or a datetime.

[thelmuth]

You can do whatever you want with the JSON printing.

As a note: There is a :json-log-filename Push arg, which you can use to not only change the filename, but also location -- if you set it to "results/experiment1/log53.json", then it will be in that subdirectory. I'd recommend not making it too determined where the JSON log goes, so that someone could change this to pick somewhere else.

[Vaguery]

Yes that is good advice.

[Vaguery]

I'll try to work on this today.