How to add an extra column in the logs

Hello,

I would like to add an additional column in the boring logs, just for the SPT-N values. Refer to the file attached. Can anyone provide guidance?.

Thanks.

PDF

Parents
  • First I would advise you to do the log reports tutorial located here:

    (+) Logs Tutorial for Log Report Design - OpenGround | gINT | Keynetix Files - OpenGround | gINT | Keynetix - Bentley Communities

    This will get you familiar with how to better work with all the entities. In general, adding a new column as you suggested will involve the following steps for your particular log form.

    1. Make a copy of the log page with a different name first.  This will allow you to go back to the way you found it if it doesn't work

    2.Decide on a width for the new column.  The column gas to be wide enough to hold the largest expected output at the desired font size for your case something in the range of 0.3 to 0.5 inches would probably work.

    3. You will have to move all of the entities to the right of the new column location the desired column width to the right.  This is easiest done with the offset move command. This will make room for your new column

    4. You will need to add a new column entity in the space that you just made.  For your case, it will probably be easiest to use the offset copy command to copy the existing SPT column entity to the new location, then adjust the width of the new copied column then delete text code to create the SPT blow counts from the entity.  You will then need to edit the original SPT entity to remove the N60 text from that entity.

    5. Edit the column widths and x locations of all columns that were moved.  You will have to make up for the space you used to create the new column at some point.  Since your log is set up as a smart log this can get complicated.  You may also have to adjust the x offset property of these entities. If columns to the left of the new column are set up as smart columns you will have to write the appropriate x offset expression to accommodate the case when the columns are not printed.

    6. You will have to adjust x coordinates of an pointers, range lines, etc that were referenced to the original column locations.

    This sounds simple but these general steps include many fine and subtle details that will need to be worked out. Count on a significant amount of time to debug the new log for multiple different data sets.

Reply
  • First I would advise you to do the log reports tutorial located here:

    (+) Logs Tutorial for Log Report Design - OpenGround | gINT | Keynetix Files - OpenGround | gINT | Keynetix - Bentley Communities

    This will get you familiar with how to better work with all the entities. In general, adding a new column as you suggested will involve the following steps for your particular log form.

    1. Make a copy of the log page with a different name first.  This will allow you to go back to the way you found it if it doesn't work

    2.Decide on a width for the new column.  The column gas to be wide enough to hold the largest expected output at the desired font size for your case something in the range of 0.3 to 0.5 inches would probably work.

    3. You will have to move all of the entities to the right of the new column location the desired column width to the right.  This is easiest done with the offset move command. This will make room for your new column

    4. You will need to add a new column entity in the space that you just made.  For your case, it will probably be easiest to use the offset copy command to copy the existing SPT column entity to the new location, then adjust the width of the new copied column then delete text code to create the SPT blow counts from the entity.  You will then need to edit the original SPT entity to remove the N60 text from that entity.

    5. Edit the column widths and x locations of all columns that were moved.  You will have to make up for the space you used to create the new column at some point.  Since your log is set up as a smart log this can get complicated.  You may also have to adjust the x offset property of these entities. If columns to the left of the new column are set up as smart columns you will have to write the appropriate x offset expression to accommodate the case when the columns are not printed.

    6. You will have to adjust x coordinates of an pointers, range lines, etc that were referenced to the original column locations.

    This sounds simple but these general steps include many fine and subtle details that will need to be worked out. Count on a significant amount of time to debug the new log for multiple different data sets.

Children