[New Port Request] Viskores
Nobody has claimed this yet.
- Dominant language
- CMake
- Stars
- 27.5k
- Forks
- 7.7k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 321
Description
Library name
Viskores
Library description
Viskores is a toolkit of scientific visualization algorithms for extremely multithreaded/parallelized processor architectures (I.e., GPUs) and high performance computing.
Importantly, Viskores replaces VTKm, which has been discontinued as of version 2.3.0.
From the Viskores repository:
Viskores is a toolkit of scientific visualization algorithms for emerging processor architectures. Viskores supports the fine-grained concurrency for data analysis and visualization algorithms required to drive extreme scale computing by providing abstract models for data and execution that can be applied to a variety of algorithms across many different processor architectures.
Source repository URL
https://github.com/viskores/viskores
Project homepage (if different from the source repository)
Anything else that is useful to know when adding (such as optional features the library may have that should be included)
Due to the discontinuation of VTKm, many libraries and packages are currently in the process of migrating from VTKm to Viskores. It would be good to have a Viskores port ready in advance :)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Viskores source repository and its build instructions, then compare existing vcpkg ports for similar C++ visualization libraries. Confirm the port can obtain and build the requested Viskores release and that vcpkg's package checks pass; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100