BASH scripting questions

[Plutie]

As a part of the script I'm working on (https://www.mersenneforum.org/showthread.php?t=27185) for automating NFS polynomial optimization, for every line in a given file, I'm looking to convert a single line of space-delimited numbers into a set of lines, each with one of those numbers (discarding the last two), i.e.

120 -11281742212640 722045358858476258138115 2694891023958331982083306 -83933374113179207162110170423420169 -27085510659298648315702935344138665 51773992299728647 -130923698301412860609805316167401612 -1.26 1.024483e+25

into:

n: input_number
c5: 120
c4: -11281742212640 
c3: 722045358858476258138115 
c2: 2694891023958331982083306 
c1: -83933374113179207162110170423420169 
c0: -27085510659298648315702935344138665 
Y1: 51773992299728647 
Y0: -130923698301412860609805316167401612

What would be the best way to go about doing this? I saw some other solutions online using awk, but I don't know how I would apply that to my problem because of the different prefixes used. (https://unix.stackexchange.com/quest...umbering-order)

[paulunderwood]

#!/bin/bash

while read line; do
    larray=($line)
    echo "n: input_number"
    echo "c5: ${larray[0]}"
    echo "c4: ${larray[1]}"
    echo "c3: ${larray[2]}"
    echo "c2: ${larray[3]}"
    echo "c1: ${larray[4]}"
    echo "c0: ${larray[5]}"
    echo "Y1: ${larray[6]}" 
    echo "Y0: ${larray[7]}"
done < $1

Put this in a file called, say, to_column.sh, run chmod u+x to_column.sh and use as ./to_column.sh <any_file> where any_file holds the lines.

[Plutie]

Originally Posted by paulunderwood

#!/bin/bash

while read line; do
    larray=($line)
    echo "n: input_number"
    echo "c5: ${larray[0]}"
    echo "c4: ${larray[1]}"
    echo "c3: ${larray[2]}"
    echo "c2: ${larray[3]}"
    echo "c1: ${larray[4]}"
    echo "c0: ${larray[5]}"
    echo "Y1: ${larray[6]}" 
    echo "Y0: ${larray[7]}"
done < $1

Put this in a file called, say, to_column.sh, run chmod u+x to_column.sh and use as ./to_column.sh <any_file> where any_file holds the lines.

Thank you! I modified it slightly to work easily with my script.

convert_polys.sh:

#!/bin/bash
# Convert msieve raw poly to CADO format
number=$2
while read line; do
    larray=($line)
    echo "n: $number" 
    echo "c5: ${larray[0]}" 
    echo "c4: ${larray[1]}" 
    echo "c3: ${larray[2]}" 
    echo "c2: ${larray[3]}" 
    echo "c1: ${larray[4]}" 
    echo "c0: ${larray[5]}" 
    echo "Y1: ${larray[6]}" 
    echo "Y0: ${larray[7]}"
    echo
done < $1

polyFinder.sh:

...
if [[ "$VERIFICATION_STRING" =~ $CADO_REGEX ]]; then
    echo File is valid sopt input.
else
    echo Invalid input, attempting to reformat.
    # pass off to separate script, convert msieve to cado format
    ./convert_polys.sh $POLYFILE $NUMBER > formatted
    POLYFILE=formatted
...

[VBCurtis]

Note that you may wish to name this mini-script something about degree 5, since it would not work in the case where the poly lines are degree 6 (GNFS 211-ish-plus).
Or is it best to just assume the script is working with degree 5 polys only?

[Plutie]

Originally Posted by VBCurtis

Note that you may wish to name this mini-script something about degree 5, since it would not work in the case where the poly lines are degree 6 (GNFS 211-ish-plus).
Or is it best to just assume the script is working with degree 5 polys only?

Honestly, that totally slipped my mind. I'll probably make two separate versions, called by the main script based on the degree parameter.

[EdH]

I modified my script to work all the way to degree 8, by checking the number of array elements and using if-then conditionals to add in the needed coefficients.

[Plutie]

another issue!

How would I reformat a set of lines given a certain order of initial characters? i.e.

 
n: 1271515007705102652189952725761191819303345301747516657201545585841235185390068713842394904588907747685724022636366668603115951556046696630803051897639628872247236774090687993328825102782693109 
Y0: -35164392518977695245121325949318512206  
Y1: 330529894414407689  
c0: -7834044196107389385481722033436772196487802910080  
c1: 32695287468220878145255421865209242060304  
c2: 166758603406144019739995422783832  
c3: -374511489403856061344417  
c4: -1148136776700228  
c5: 189189  
skew: 534376440.24

becomes:

 
n: 1271515007705102652189952725761191819303345301747516657201545585841235185390068713842394904588907747685724022636366668603115951556046696630803051897639628872247236774090687993328825102782693109
c5: 189189
c4: -1148136776700228
c3: -374511489403856061344417
c2: 166758603406144019739995422783832
c1: 32695287468220878145255421865209242060304
c0: -7834044196107389385481722033436772196487802910080
Y1: 330529894414407689
Y0: -35164392518977695245121325949318512206  
skew: 534376440.24

I'm pretty sure this is the last bit I need to have full compatibility with all (hopefully) formats of polynomials being sent here.

[paulunderwood]

#!/bin/bash

readarray lines < $1
echo ${lines[0]}
i=1
j=${#lines[@]}
while ! [[ ${lines[$i]} =~ "skew" ]]; do
    i=$(expr $i + 1)
    echo ${lines[$(expr $j - $i )]}
done
echo ${lines[$i]}

HTH

[Plutie]

Originally Posted by paulunderwood

#!/bin/bash

readarray lines < $1
echo ${lines[0]}
i=1
j=${#lines[@]}
while ! [[ ${lines[$i]} =~ "skew" ]]; do
    i=$(expr $i + 1)
    echo ${lines[$(expr $j - $i )]}
done
echo ${lines[$i]}

HTH

Thank you! Works great, except that the n value becomes empty (and the actual number gets moved right above the skew value)

...
Y1: 330529894414407689 
Y0: -17582196259488608100436846735568937674 
 1271515007705102652189952725761191819303345301747516657201545585841235185390068713842394904588907747685724022636366668603115951556046696630803051897639628872247236774090687993328825102782693109
skew: 256945061.15
 

[paulunderwood]

I don't understand how it loses "n:". The first line must be n and its value and not an empty line. It could be a better script, dropping "j".

[Plutie]

Originally Posted by paulunderwood

I don't understand how it loses "n:". The first line must be n and its value and not an empty line. It could be a better script, dropping "j".

Spotted the issue, for some reason the number for "n:" was on a new line somehow.