From 16279bb2243b0bcf28efd2428448935a6e5ea9bc Mon Sep 17 00:00:00 2001 From: esther Date: Tue, 7 May 2024 22:26:36 +0200 Subject: [PATCH] wrote on report --- documentation/report.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/documentation/report.md b/documentation/report.md index 3cdc274..19472fc 100644 --- a/documentation/report.md +++ b/documentation/report.md @@ -9,9 +9,12 @@ The cli interface is `gdal_contour [OPTIONS] ` with # data structure and input/output ![](ER_diagram.svg) # Responsibilities: -Esther will create the algorithm itself with multitreading. This will essentially be a function that takes a grid of pixels as input and returns a similar grid of cells. +Esther will create the algorithm itself with multithreading. This will essentially be a function that takes a grid of pixels as input and returns a similar grid of cells. Trygve will take care of reading in the tiff file into our own datastructure and creating a vector image from the output of the algorithm. +# Special interest +Calculated some statistical estimates for the average, variance and standard deviation for the pixels in the image. Also tried to calculate the steepness around each pixel. However, we didn't manage to get the Gdal to work for this. + # How do you plan to make it easily verifiable that your objectives are reached? We can compare against the `gdal_contour` cli program which is a implementation widely used in other software. We can compare speed, memory usage and the result itself. Each step in our program also produces a output which we can be worked on and evaluated independently. \ No newline at end of file