50 | | There are no weekly reports at this time. |
| 50 | ==== Week 01 ==== |
| 51 | 1. What did you get done this week? |
| 52 | - Built GRASS73 from source from my local repo directoy. |
| 53 | - Stepped into a module (v.in.ascii) using the debugger to watch it work at the source code level. This was only proving the concept of stepping into the code – just getting it to work. |
| 54 | - Talked with my mentor about the nature of the existing v.in.pdal module and what are some of the things which must be changed, fixed, or improved. |
| 55 | |
| 56 | |
| 57 | 2. What do you plan on doing next week? |
| 58 | - Continue stepping through v.in.ascii to see how it works at the source level in order to understand how to write points to a vectormap. |
| 59 | - Get GRASS 73 to link to current version of PDAL. |
| 60 | - Fix broken references to PDAL data structures in the GRASS source |
| 61 | - Refactor existing v.in.pdal so that operations which r.in.pdal and r3.in.pdal will need are in a separate module and available as functions to be called from all three of them. |
| 62 | - Learn the process of calling PDAL and how to get it to do the basic operation of reading a lidar file and handing over the data to the caller. |
| 63 | - Set up a basic set of test data for PDAL, open it from pdal without GRASS, then open it using pdal through GRASS with only the most basic options in operation. |
| 64 | - Get PDAL to be able to read .laz (compressed) files. For some reason it can’t do that after build-from-source. |
| 65 | |
| 66 | 3. Are you blocked on anything? |
| 67 | At the moment I can’t remember how to change the execution command so as to debug GRASS .c modules in QTCreator. Vashek did it in a few days ago while I was there, but I did not write it down, and now I can’t find it. I have a question in for him and Anna about this via email. |
| 68 | |
| 69 | When I try to run v.in.ascii on GRASS73 on Linux, I just get errors: |
| 70 | ERROR: Option <input> does not accept multiple answers |
| 71 | ERROR: Option <output> does not accept multiple answers |
| 72 | ERROR: Option <separator> does not accept multiple answers |
| 73 | ERROR: Option <skip> does not accept multiple answers |
| 74 | ERROR: Option <z> does not accept multiple answers |
| 75 | |
| 76 | I am awaiting approval on the GRASS User mailing list to ask what I should do different. Note the command is generated via dialog box on GRASS73, and when I run it on GRASS72 on the Windows side it runs just fine. |
| 77 | |
| 78 | |
| 79 | |