HOWTO: VinDSL Conky Script

[Cavsfan]

Helloooo

I had noticed this error some moons back during my daily check of wx around the planet - I had noticed that the 10th day low temp forecast was NA. I keep one conky display on world weather - Please confirm if you are still getting this message then can you send me the currdata.html from the conkywx temp directory under the /tmp. thanks

It does not affect the output but the warning is a good thing.

I have made changes to the new version. I have been working on the new version for some time - time is a major challenge some times lol

Also need to work on the wiki - have started but lets see

cheers

Helloooo

I am not getting the error or the display by Moonset any longer.

Seen it on more than one ubuntu yesterday but today everything is good.

cheers

[paramvir]

Helloooo

I am not getting the error or the display by Moonset any longer.

Seen it on more than one ubuntu yesterday but today everything is good.

cheers

Fantastic

Regarding the moon and the sun - they do not rise and set in the same way.

Just a small explanation

Moon has the same side always facing the Earth - this is a habit of most satellite moons - or so I have understood. Our Sun spins at a certain rate which gets adjusted every leap year. Oh and there is nothing as Dark side of the Moon - that is just Pink Floyd lol - That side is just the side we cannot see from Earth!!!

Our moon has 1 lunar month of 29d 12h 44m 03s [2.86s actually] - this is solar time - so in solar 24 hours - that is the actual time for a lunar month.

Which means that there will be times when within your 24 solar hours the moon may not set or rise.

Soooo - it may rise today and set tomorrow - you get A.A.H ~ always above horizon - no setting time for the moon today!

Or you may have moon set today and rise another day but not the day you are looking at - A.B.H. ~ always below horizon.

Our bellowed Sun also has these issues - but in the polar latitudes.

That is why you do not have that Moonset thing - that happened that day - now both rise and set times fall within your solar 24 hour day.

cheers

[Cavsfan]

Fantastic

Regarding the moon and the sun - they do not rise and set in the same way.

Just a small explanation

Moon has the same side always facing the Earth - this is a habit of most satellite moons - or so I have understood. Our Sun spins at a certain rate which gets adjusted every leap year. Oh and there is nothing as Dark side of the Moon - that is just Pink Floyd lol - That side is just the side we cannot see from Earth!!!

Our moon has 1 lunar month of 29d 12h 44m 03s [2.86s actually] - this is solar time - so in solar 24 hours - that is the actual time for a lunar month.

Which means that there will be times when within your 24 solar hours the moon may not set or rise.

Soooo - it may rise today and set tomorrow - you get A.A.H ~ always above horizon - no setting time for the moon today!

Or you may have moon set today and rise another day but not the day you are looking at - A.B.H. ~ always below horizon.

Our bellowed Sun also has these issues - but in the polar latitudes.

That is why you do not have that Moonset thing - that happened that day - now both rise and set times fall within your solar 24 hour day.

cheers

Wow! Thanks for the explanation! I had no idea about any of that. So, when I see A.A.H. or A.B.H. I will know that it is not a problem.
The Pink Floyd analogy is pretty cool too. I had no idea one side of the moon never faces us.

cheers

[paramvir]

I have just scratched a script for getting music information - you already have this in the VinDSL template - but I wanted a single line - no matter what player I am using - I use smplayer and vlc - or both at the same time

There are 2 ways you can use it

1. template1 path-to-file/music_sorter.sh
2. template1 path-to-file/music_sorter.sh "SMPlayer"

In the 1st case - if you have configured the 2 player in the script they get activated and you get Alerts kind of display but with your players marked with :: as separator on the same single line.

In the second case you define the player and it will work like you have the long script at present.


music_sorter.sh

#!/bin/bash

UserChoice="$1"

if  [[ ! $UserChoice ]]; then
    ## Single scroller for multiple players
    # add the name of the player as seen in the xlsclients output
    players=( "SMPlayer" "VLC media player" )
    # add name here as you would like to see in the scrolling text
    short_player_name=( "SMPlayer" "VLC" )
    
    for c in ${!players[@]}
    do
        get_track=$(/usr/bin/xlsclients -l | grep "${players[$c]}" )
        if [[ $get_track ]]; then
            get_track="::${short_player_name[$c]}:: ${get_track/Name: /}"
            g_track+=( "${get_track/- "${players[$c]}"/ }" )
        fi
    done
    g_track=${g_track[@]/#/ | }
    g_track=${g_track/|/}
else
    ## Scroller for each player as defined
    get_track=$(/usr/bin/xlsclients -l | grep "$UserChoice" )
    if [[ $get_track ]]; then
        get_track="${get_track/Name: /}"
        g_track=( "${get_track/- "$UserChoice"/ }" )
    fi
    g_track="${g_track[*]}"
fi

echo "${g_track}"

exit 0 

my line for the single scroller

${if_empty ${exec ${template1}}}${voffset 2}${color4}${hr 2}${else}\
${voffset 2}${font Dejavu Sans:bold:size=10}${color1}Media Playing ${color4}${voffset -2}${hr 1}
${voffset 4}${color3}${if_match ${execi 10 expr length "$(${template1})" }>=34}${color3}${scroll 34 10 ${execi 10 ${template1}}}
${color4}${hr 2}${color3}${else}${alignc}${execi 10 ${template1}}
${color4}${hr 2}${font}${endif}${endif}

NJoy

[Cvetan]

I suddenly started getting error when starting conky. It looks like all working fine but look at the error:

Conky: desktop window (1800095) is subwindow of root window (159)
Conky: window type - override
Conky: drawing to created window (0x3200001)
Conky: drawing to double buffer
/usr/share/conkywx/conkywx.sh: line 660: 08: value too great for base (error token is "08")
/usr/share/conkywx/conkywx.sh: line 663: 08: value too great for base (error token is "08")
/usr/share/conkywx/conkywx.sh: line 670: 08: value too great for base (error token is "08")

And here is the content of the file that is referencing:

for l in ${!nowdata[@]}
        do
            if [[ "${nowdata[$l]}" == "N/A" || "${nowstored[$l]}" == "N/A" ]]; then
                trend1="-"
                trend_arrow1="-"
            else
                    if [[ ${nowdata[$l]} -eq ${nowstored[$l]} ]]; then <-this is line 660 in the file
                    trend1="Steady"
                    trend_arrow1=$( echo -e $steadytrend )
                elif [[ ${nowdata[$l]} -lt ${nowstored[$l]} ]]; then
                    if [[ $l -gt 6 ]] && [[ $l -lt 11 ]]; then
                        trend1="Ealier"
                    else
                        trend1="Falling"
                    fi
                    trend_arrow1=$( echo -e $fallingtrend )
                elif [[ ${nowdata[$l]} -gt ${nowstored[$l]} ]]; then
                    if [[ $l -gt 6 ]] && [[ $l -lt 11 ]]; then
                        trend1="Later"
                    else
                        trend1="Rising"
                    fi
                    trend_arrow1=$( echo -e $risingtrend )
                else
                    trend1="-"
                    trend_arrow1="-"
                fi
            fi

            trend+=( $trend1 )
            trend_arrow+=( $trend_arrow1 )
        done
    local time_diff2=$(( nowtime1 - ${trends_store[0]} ))
    local time_diff_time=$(( nowtime1 - ${trends_time_store[0]} ))

    # trend_out - total trend array output
    trends_out=( "${trend[@]}" "${trend_arrow[@]}" )

[paramvir]

[QUOTE=Cvetan;12737350] 08: value too great for base (error token is "08")
[/CODE]

This is a standard bash error where it thinks this is hex number as there is a leading zero.

But this was handled since version 9 he he the pesky zero and bash.

I have tried looking at Belgrade - cannot see it.

Can you send me the debug file.

You can also look in the conkywx assistant to view the trend data. I am wondering how that number got in with the leading zero

Include that trend output with the debug file.

Basically which value is it - that starts with 08 - that Sir is that $$$ question.

cheers

[Cvetan]

Here is the debug file. Had to change extension since forum didn't allow with .log to be uploaded.

[paramvir]

Here is the debug file. Had to change extension since forum didn't allow with .log to be uploaded.

Many thanks for that file. I had to finally use manual data to re-create that error - and found that perhaps we had a 2 decimal value where normally we expect 1 decimal value. So a value like 0.08 came in which got cleaned to 08.

That really helped me for the next version which is mostly in perl - where a leading 0 gets taken as an octal value lol - you have to watch that leading zero

    ft_data=( "$Pressure" "$Temp_now" "$wind_speed_trend" "$Humidity" "$uv2" "$Dew_Point" "$Visibility" )
    # ft_data=( "1020 hpa" "16°C" "0.08 km/h" "70" "0.7 : low" "0°C" "0.7 km" )
    shopt -s extglob
    for l2 in ${!ft_data[@]}
    do
        ft_data[$l2]=${ft_data[$l2]/°*}        # clean deg symbol
        ft_data[$l2]=${ft_data[$l2]/ *}        # clean spaces
        ft_data[$l2]=${ft_data[$l2]//[.]/}     # clean the rest
        ft_data[$l2]=${ft_data[$l2]##+(0)}     # clean leading zero
        ft_data[$l2]=${ft_data[$l2]:-0}        # 0 if value is 0
    done
    # msgout "${ft_data[*]}"

    # changes 24 hours
    ft2_time=( $sun_rise $sun_set $moon_rise $moon_set "$length_visible_light" "$length_day" $percentilluminated )
    # ft2_time=( 0656 1813 0 0059 1204 1116 00 )
    for l1 in ${!ft2_time[@]}
    do
        ft2_time[$l1]=${ft2_time[$l1]/always*/NA}     # clean the rest
        ft2_time[$l1]=${ft2_time[$l1]//[.:h m]/}     # clean the rest
        ft2_time[$l1]=${ft2_time[$l1]##+(0)}         # clean leading zero
        ft2_time[$l1]=${ft2_time[$l1]:-0}             # 0 if value is 0
    done
    shopt -u extglob

At present you have the blue line some where below the orange line - just move it like you see above and you will not get that error again.

While you will not get an error - I know the result will not give you correct trend when the value changes - 0.08 is less than 1 if that is the next value but it will show reverse trend as 8 is greater than 1. This has been an issue and is fixed in the next version. Weekends I get more time to look into all this sooooo

cheers

[VinDSL]

Wanted to pop in here. I'm still alive (if anybody cares). LoL!

I'm just very, very, busy right now, with real-world issues, that cannot be ignored.

@paramvir: You're doing a great job, man! Thanks, for keeping the thread alive!

Here's my current GNOME3 (3.9.4) Staging desktop. ConkyWX is working like a champ!

Ubu 13.10 / GS 3.9.4 / Linux 3.11-rc1 mainline kernel / nVidia 304.88 - patched for 3.11 / ConkyWX 0.9.3

When I get a chance, I'll publish an update of my config files. It's well overdue. Sorry, it's taking so long!

[paramvir]

Wanted to pop in here. I'm still alive (if anybody cares). LoL!

I'm just very, very, busy right now, with real-world issues, that cannot be ignored.

@paramvir: You're doing a great job, man! Thanks, for keeping the thread alive!

Here's my current GNOME3 (3.9.4) Staging desktop. ConkyWX is working like a champ!

When I get a chance, I'll publish an update of my config files. It's well overdue. Sorry, it's taking so long!

he he looks like we are back in action - we are an effective team huuaaaa ha ha ha lol

Last I saw your msg and got that thing in place - grrrrrr

yeah - this may surprise you amigo but YES we do care you are alive lol

That desktop looks good - conkywx is progressing quite well - documentation kills man - really !!!

It is good to have things rolling