Closed alxbilger closed 5 months ago
@alxbilger you did not keep the (git) history of the files when moving to the new plugin.
@alxbilger you did not keep the (git) history of the files when moving to the new plugin.
It's such a pain. I suspect you don't like me much to request such a task. In this branch https://github.com/alxbilger/CSparseSolvers/tree/move_csparse_files, I have the same plugin but with all the SOFA history. I guess it's not really what we want neither. Do you know how to proceed?
@alxbilger you did not keep the (git) history of the files when moving to the new plugin.
It's such a pain. I suspect you don't like me much to request such a task.
🥰
In this branch https://github.com/alxbilger/CSparseSolvers/tree/move_csparse_files, I have the same plugin but with all the SOFA history. I guess it's not really what we want neither. Do you know how to proceed?
I would proceed like this:
Credit to @hugtalbot https://github.com/sofa-framework/sofa/issues/1442
@fredroy the history is now preserved
[ci-build][with-all-tests][force-full-build]
[ci-depends-on] detected during build #5.
To unlock the merge button, you must
@fredroy the history is not preserved
It does now no ? I can see commits down to Commits on Mar 10, 2009
? (a9bd817a4ec46a06e07b9f755660c58d48cf9d17)
@fredroy the history is not preserved
It does now no ? I can see commits down to
Commits on Mar 10, 2009
? (a9bd817)
Yes, it is preserved
[ci-build][with-all-tests][force-full-build]
[ci-depends-on] detected during build #6.
To unlock the merge button, you must
[ci-depends-on] detected during build #7.
To unlock the merge button, you must
@alxbilger it seems that some scenes which use EigenSimplicialLLT
instead of a CSparse-based linear solver are crashing, maybe because of the default template CSRMat3x3
Why is the minimum cmake version of CSparsePlugin 3.24 -> ci won't work if it stays like that. I've configured it with 3.22 (shipped version of Ubuntu 22.04) and it works fine. (I know not exactly in this PR, but this is the pr that propose the CSparePlugin creation)
@bakpaul The 3.24 version of CMake was in anticipation of @olivier-roussel's work on fetching mechanism. But since the 3.24 version is no longer required, it could be the same than SOFA.
TODO: save the previous scenes in the new plugin
[ci-depends-on] detected during build #8.
To unlock the merge button, you must
[ci-build][with-all-tests][force-full-build]
[ci-build][with-all-tests][force-full-build]
[ci-depends-on] detected during build #10.
To unlock the merge button, you must
@bakpaul This PR does not take the latest commits in sofa-framework/ci. Hence, it does not fetch and compile the plugin CSparseSolvers. Here is what I see in the logs:
--------------- Clone CI scripts ---------------
pwd = /builds/workspace/sofa-framework/PR-4258/ubuntu_gcc_options_release
Cloning into 'ci'...
640400517e592bfa826a46dea29b6ddd512abf02 Merge pull request #21 from hugtalbot/202308_remove_meshsteploader_from_list
CI scripts are available in /builds/workspace/sofa-framework/PR-4258/ubuntu_gcc_options_release/ci/scripts
It's not the latest commit in the master branch. Can you investigate why?
My bad, I modified the CI to checkout before your changes because I though that I merged too early, but I finally realized that it was useless. So back to normal !
ok thanks ;)
[ci-build][with-all-tests][force-full-build]
[ci-depends-on] detected during build #11.
To unlock the merge button, you must
[ci-depends-on] detected during build #12.
To unlock the merge button, you must
[ci-build][with-all-tests][force-full-build]
They are moved in an external plugin: https://github.com/sofa-framework/CSparseSolvers
Two components are impacted:
SparseLUSolver
andSparseCholeskySolver
.The plugin
CSparseSolvers
is now fetchable[ci-depends-on https://github.com/sofa-framework/SofaPython3/pull/378] [ci-depends-on https://github.com/sofa-framework/BeamAdapter/pull/119]
By submitting this pull request, I acknowledge that
I have read, understand, and agree SOFA Developer Certificate of Origin (DCO).
Reviewers will merge this pull-request only if