Tima version: 2022-4
LHS version:DeltaTima version:GeometryServer version:FMS type:
Client: Centinela
Diagnosis and Solution:
The weekly plan was loaded in Centinela QA using delta tima and everything appears in order (indicators, solids, etc).
Then a load of the same weekly plan was loaded in Centinela PROD. It's observed in TIMA that the solids were generated according to the plan and were correctly colored according to their category, in addition the percentage of mine movement and spatial compliance were calculated, but the conciliation indicators in Kton for the 5 categories appear at 0.
The following procedures were performed to resolve the issue:
- Refresh all and Refresh legend in Postman: didn't fix the problem
- Plan Reload: Didn't fix the problem
- Clean reload of the plan by entering geometric server: didn't fix the problem
- Postman review, the endpoint showed the same as the front (Kt indicators at 0 and compliance and relocated values are according to what is shown in TIMA). Front bug has been ruled out.
- In Postman it was changed from 5 categories to 3 categories to rule out that the widget was dead. The indicators were still showing at 0 only with 3 categories.
- In postman, a GET was carried out for compliance and the problem was identified: In Centinela QA there were values of volumes and tons but in Centinela PROD the volume indicators had values but the kilotonnes did not. The problem was related to the block model (which is necessary to transform from volume to tons according to the density of the block).
The block model in Minio was revised for both environments: In Geometry-Server --> STA --> BlockModel.
It was verified that the block model loaded in both environments was the same, with the following format:
Since the block models were the same, it means that there must have been a difference in the block model configuration. There is a JSON that configures the block model, we find this in the same Minio for each environment in Geometry-Server --> STA --> metadata --> blockModel.json.
When reviewing both, it was observed that they were not the same, the order of the columns was not the same and neither was the separator:
blockModel.json which worked in Centinela QA:
blockModel.json NOT working on Centinela PROD:
It is very important that the correct separator of the block model file is set and the correct order that the block model must have:
0: X coordinate
1: Y coordinate
2: Z coordinate
3: Block dimension in X
4: Block dimension in Y
5: Block dimension in Z
6: Density
7: Cut
We edit the JSON and replace it in the Minio. To make sure that the modification of the widget in TIMA is displayed, you must go to Postman and in the selected environment make a POST to the refresh legend and then a POST to the compliance charts settings. It's recommended to close TIMA and reopen it.
Why this problem occurs has not yet been identified, since before loading the week (as it had been done before and in the other environment) the block model was well configured in its order and separator. The block model configurations for both environments were the same, so Centinela PROD had not had this problem before. In the event that the volumes are shown in Postman and the block model is the same for both environments, the configuration of blockModel.json should be reviewed as it could have been misconfigured in Minio.