- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 11 2020
Nov 10 2020
Nov 9 2020
will check old documentation/nature communications example
will set a message in as.challenge() that na.treat needed for report and sanity check in report()
Nov 7 2020
All build configuration now works on Windows, Ubuntu, and macOS. OpenMesh also integrated but the remeshing/decimation is not yet implemented to replace the old functionality of ACVD.
Nov 6 2020
Found very old isolated code (everything related to mitk::Mesh), that I would like to drop instead of migrate. Seems to be from the time when Visual C++ 6.0 was a thing. :D
should be working but hasn't been really tested lately. only applies to rank then aggregate. originates from nature communications paper and should be explained there.
For testing I could again compare to Annette's code used at that time.
Wouldn't drop it but you are right that documentation is missing
Nov 5 2020
Pushed new branch feature/T27931-OpenMesh.
Migrating ACVD to VTK 9 is not a trivial task as it heavily depends on VTK's data structures that fundamentally changed between VTK 8 and VTK 9. I already spent some hours and managed to compile ACVD but I still get runtime errors related to all the indexing in data structures. Given that ACVD is maintained by only a single person and most of the upgrades over the past years were contributions, I really think that we should look for alternatives to replace ACVD. Its choice to be deeply entangled with VTK for mesh processing added a lot of complexity and I really want to get rid of the additional VTK dependency. There were some advancements over the past years in terms of remeshing/mesh decimation and I already found solid CMake-based, license-friendly alternatives like OpenMesh.
This task can be closed. Future work on this is done in T27923.
This task can be closed. Future work on this is done in T27923.
This task can be closed. Future work on this is done in T27923.
This task can be closed. Future work on this is done in T27923.
I migrated the old branch to the changes in develop since June.
Pushed new branch feature/T27461-VTK9.
Deleted branch feature/T27461-VTK9.
Nov 4 2020
I'm using R 4.0.2 since summer without issues
also roxygen import and also intitialization of S3 methods have to be written in roxygen then and the namespace file is then entirely written by roxygenization (ideally indcluding help)
I started with the roxygen documentation and found that the NAMESPACE file can be generated automatically by using the "export" tag.
I did not try it yet. Did you? Currently, I don't want to take the risk of breaking my running development environment.
The legend could be moved to the bottom.
Pushed new branch feature/T27923-python-dev.
Deleted branch bugfix/T26745-MinorFixes.
Pushed new branch bugfix/T26745-MinorFixes.
Deleted branch bugfix/T27926-ImproveGizmoInteraction.
Pushed new branch bugfix/T27926-ImproveGizmoInteraction.
Deleted branch bugfix/T26745-MITK-VTK-Interaction.
Pushed new branch bugfix/T26745-MITK-VTK-Interaction.
Deleted branch feature/T27247-ShowConsoleWindow.
Pushed new branch feature/T27247-ShowConsoleWindow.
Nov 3 2020
I think this may be closed. There have not been any problems with R 4 and R 4 is generally unproblematic.
Agreed?
hm, how do you propose to deal with that? Adapt font size of algorithm names? These might get tiny then....
Pushed new branch feature/T27923-execute-python-code-in-mitk.
Nov 2 2020
Deleted branch bugfix/T27920-ReduceDoxygenWarnings.