Error: failed to install CRD crds/crds.yaml: CustomResourceDefinition.apiextensions.k8s.io "tlsstores.traefik.containo.us" is invalid: [spec.versions: Invalid value: []apiextensions.CustomResourceDefinitionVersion(nil): must have exactly one version marked as storage version, status.storedVersions: Invalid value: []string(nil): must have at least one stored version]
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 26 2021
Nov 25 2021
It seems to me like this was done in this commit. Can the task be closed?
Pushed new branch T28875-OdfNormalization.
Nov 24 2021
I implemented a fix which includes your suggestion to extend the interfaces of the TranferFunctionWidget and QmitkTransferFunctionGeneratorWidget @floca. This resolves the issue that the histogram is not updated. Additionally, to also update the volume that is shown in the 3D render window, I extended the mitkVolumeMapperVtkSmart3D to also work with the correct timesteps. Before this change, only a volume for timestep 0 was created. With this fix, the workbench also does not crash with the Heart3D+t dataset.
Pushed new branch to rMITK MITK: bugfix/T28274-volumerendering-multiple-timesteps.
Nov 23 2021
ubuntu@vm-129-189:~$ ./install_platform.sh USER: ubuntu Check disk space: ok SIZE: 194G Check if helm is available... ok Get helm deployments... Error: Kubernetes cluster unreachable: the server has asked for the client to provide credentials
ubuntu@vm-129-189:~$ kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE base code-server-7b9b68c556-fqrc9 1/1 Running 3 84m base landingpage-7c7bb855b-hz484 1/1 Running 3 86m default kaapana-exp-extensions-87rjt 0/1 Completed 0 84m default kaapana-plugin-kqdd2 0/1 Completed 0 84m default kaapana-stab-extensions-ktk29 0/1 Completed 0 84m flow-jobs dcmsend-00382388 0/1 Completed 0 81m flow-jobs dcmsend-2b49b0c7 0/1 Completed 0 80m flow-jobs dcmsend-5ff032fb 0/1 Completed 0 81m flow-jobs dcmsend-98c4d2c3 0/1 Completed 0 81m flow-jobs dcmsend-e2633395 0/1 Completed 0 81m flow airflow-6ddc54d9b4-hcvb6 2/2 Running 6 86m flow ctp-76cf9bbc9f-6nchk 1/1 Running 3 86m flow postgres-airflow-64954bfb86-t2bjt 1/1 Running 3 86m kube-system coredns-588fd544bf-27hc8 1/1 Running 5 91m kube-system error-pages-57598754db-fz7bc 1/1 Running 3 86m kube-system keycloak-967cbfb55-8jjsv 1/1 Running 3 86m kube-system kube-helm-deployment-7f8464f9df-tnbmg 1/1 Running 3 86m kube-system kube-state-metrics-5695698777-dq864 1/1 Running 3 86m kube-system kubernetes-dashboard-69664c8798-4lw9j 1/1 Running 3 86m kube-system louketo-687bbbf6d9-cjgxs 1/1 Running 3 86m kube-system postgres-keycloak-5cc9b468d9-pkd82 1/1 Running 3 86m kube-system preinstall-extensions-init-w9jss 0/2 Completed 0 86m kube-system traefik-5786899dff-99q9f 1/1 Running 3 86m kube-system update-extensions-init-vjhtq 0/1 Completed 0 86m meta elastic-meta-de-9885fb5b4-wcptq 1/1 Running 3 86m meta init-meta-dfpdt 0/1 Completed 0 86m meta kibana-meta-de-8f7c4bd6c-h7k94 1/1 Running 3 86m monitoring alertmanager-74fc67bd8-5zvtn 1/1 Running 3 86m monitoring grafana-6f6b5dc559-2jhcx 1/1 Running 3 86m monitoring prometheus-76bf79f68f-zcqfp 1/1 Running 3 86m store dcm4chee-78487774cf-86pkq 1/1 Running 3 86m store dicom-init-twb8d 0/1 Completed 0 86m store ldap-684f697598-lzfnj 1/1 Running 3 86m store minio-deployment-79dc7dd464-qv4sk 1/1 Running 3 86m store minio-init-76dn6 0/1 Completed 0 86m store ohif-65cdcd8b87-lhcfd 1/1 Running 3 86m store postgres-dcm4che-75d84848c5-rdqxq 1/1 Running 3 86m ubuntu@vm-129-189:~$ ubuntu@vm-129-189:~$ ubuntu@vm-129-189:~$ ubuntu@vm-129-189:~$ ubuntu@vm-129-189:~$ kubectl get nodes NAME STATUS ROLES AGE VERSION vm-129-189.cloud.dkfz-heidelberg.de Ready <none> 92m v1.21.6-3+dd57cd4fdc581a
Nov 22 2021
Here is the fix of this bug as pull request at github: https://github.com/MITK/MITK/pull/253
Pushed new branch T28872-Registration.
For the histogram part the reason is (swiftly looking into the code) that Neither the TransferFunctionWidgets nor the used histogramm classes support 4D images, the assume images to be static. But as the QmitkTransferFunctionWidget want the whole node, we cannot just use a TimePointSelector filter in the view. It seems like we need to extend the interface of the TransferFunctionWidgets (same for the QmitkTransferFunctionGeneratorWidget) in order to also set the current time step and handel it internally correctly.
I tried to reproduce this bug and for US4DCyl the behaviour was the same when I tested it (histogram remains the same for all timesteps). For Heart3D+t sometimes nothing is displayed at all (as described here) but also sometimes the workbench crashes as described in T24754. However, I could not find any pattern when which behaviour occurs. I tested it with the current release installer on Windows and on the current develop branch in Debug mode. I can try to narrow it down a bit.
Nov 19 2021
Pushed new branch T28867-FiberfoxTest.
Nov 18 2021
After some analysis, it is understood that there is a difference in the modified time of the tool and the segmentation. This is detected in the AutoMLSegmentationWithPreviewTool.DoUpdatePreview method if-case of this->GetMTime() > m_MLPreviewNode->GetData()->GetMTime().
This change in time happens because tool->IsTimePointChangeAwareOn() is called after the tool->UpdatePreview() call is made in the tool's GUI class, eg. QmitkOtsuTool3DGUI
I think there is a bug in the itk filter. itkPatchBasedDenoisingImageFilter normalizes the patch weights to center weigh=1, i.e. the other weights might very well become > 1. In a next step it is asserted that the weights are <=1, leading to a crash (PatchBasedDenoisingBaseImageFilter<TInputImage, TOutputImage>
::SetPatchWeights).
Deleted branch from rMITK MITK: bugfix/T28778-fix-rendering-tests.