Add nemesis files for the parallel exodus examples

[mattfalcone1997]

Summary

I am adding a Nemesis (Parallel Exodus) file to the data repository in anticipation of creating a PExodusIIReader in pyvista (pyvista/pyvista#8815). The data comes from the VTK data repository and hence uses the same licence as VTK.

Declared license

• SPDX identifier: BSD License 2.0
• Source URL: https://vtk.org/download/
• Commercial use: permitted
• Attribution required: Copyright (c) 2008-Present Ken Martin, Will Schroeder, Bill Lorensen. All rights reserved.

[user27182]

Can you include a license file?

Provide a license file alongside the dataset. For a dataset that has its own directory, add a LICENSE file inside it. For a dataset that sits as a loose file in Data/, add a .license companion file. The license file must contain:

The source URL.
The verbatim license statement or a link to it.
The required attribution text, if any.
An SPDX-License-Identifier: line.

for the url, is there a direct download link available for the new files?

[mattfalcone1997]

Can you include a license file?

Provide a license file alongside the dataset. For a dataset that has its own directory, add a LICENSE file inside it. For a dataset that sits as a loose file in Data/, add a .license companion file. The license file must contain:
The source URL.
The verbatim license statement or a link to it.
The required attribution text, if any.
An SPDX-License-Identifier: line.

for the url, is there a direct download link available for the new files?

I can just include the VTK copyright notice which is from the BSD-2.0 licence, if that is sufficient? I'm not sure there is a direct download for the new files only the entire VTK data tarball. THe VTK gitlab does have checksums for the files though.

[user27182]

Okay it seems it's rather non-obvious how to get the files directly. I think this works? You can get all the files this way by replacing the SHA512 checksum.

It would be good to include these links specifically as the file source for future reference / easy retrieval.

• can.e.4.0
  https://www.vtk.org/files/ExternalData/SHA512/e9fad7b012901a7757d2d446a8057598b6b99824cd9d16670ff811e62b8b48c0dc723896b5e66317ea43cc768796060e327afea9204dcc5d6ab22a3bdf90fd20

• can.e.4.1
  https://www.vtk.org/files/ExternalData/SHA512/93575fefa07767cb8e56c7f758c72e9d30909292fcaddd8723bdca0c77864382b6087c194aae151a4c5a1157e4cf9bb464a4e2d173e91012c22ffbc84d370ce1

• can.e.4.2
  https://www.vtk.org/files/ExternalData/SHA512/4af0031825cda782d4bac8451d416891c14609c4134b6c1d270821bab8827843070fbfd74064b5db4da60128dc11b2209447754908dc3d949ace5034fa061a7e

• can.e.4.3
  https://www.vtk.org/files/ExternalData/SHA512/9f6827262107bfff45d660ed6a5d914e532318b86909ae4d68cc4355114b263e1114a3d80155bc6bcc86ee5ece6d90e25db62a001cbedc836de190051c21ed9f

Re BSD license, I think that's fine to mention that, it seems like it applies to all VTK data based on this thread https://discourse.vtk.org/t/availability-of-testing-data-associated-with-vtk-and-paraview/6481

Not sure where the heated plate comes from? Maybe split the two datasets into separate dirs, and add separate LICENSE file in each subdir

[mattfalcone1997]

Okay it seems it's rather non-obvious how to get the files directly. I think this works? You can get all the files this way by replacing the SHA512 checksum.

It would be good to include these links specifically as the file source for future reference / easy retrieval.

• can.e.4.0
  https://www.vtk.org/files/ExternalData/SHA512/e9fad7b012901a7757d2d446a8057598b6b99824cd9d16670ff811e62b8b48c0dc723896b5e66317ea43cc768796060e327afea9204dcc5d6ab22a3bdf90fd20
• can.e.4.1
  https://www.vtk.org/files/ExternalData/SHA512/93575fefa07767cb8e56c7f758c72e9d30909292fcaddd8723bdca0c77864382b6087c194aae151a4c5a1157e4cf9bb464a4e2d173e91012c22ffbc84d370ce1
• can.e.4.2
  https://www.vtk.org/files/ExternalData/SHA512/4af0031825cda782d4bac8451d416891c14609c4134b6c1d270821bab8827843070fbfd74064b5db4da60128dc11b2209447754908dc3d949ace5034fa061a7e
• can.e.4.3
  https://www.vtk.org/files/ExternalData/SHA512/9f6827262107bfff45d660ed6a5d914e532318b86909ae4d68cc4355114b263e1114a3d80155bc6bcc86ee5ece6d90e25db62a001cbedc836de190051c21ed9f

Re BSD license, I think that's fine to mention that, it seems like it applies to all VTK data based on this thread https://discourse.vtk.org/t/availability-of-testing-data-associated-with-vtk-and-paraview/6481

Not sure where the heated plate comes from? Maybe split the two datasets into separate dirs, and add separate LICENSE file in each subdir

The heated plate was my own case, which I have removed in favour of the can. Should the URLs simply be stated in the PR or in the actual repo?

[user27182]

If you generated the file yourself, you can attribute your own license to it, and keep it in the repo here. It has a different extension .n, so would be worth keeping if the two formats are different .n vs .e. (I know nothing about the format and what the difference is, if any).

For the URLs, we should formally document them inside the LICENSE file so that's its logged in the repo directly, rather than just mentioned in the PR.

Have a look at the recent LICENSE file added here as an example of what to include #67