Fake Programmers

Ivo Flipse

11:42 AM

look @DMA57361, I've split up the virtual measurements based on the step lengths for running and walking

not sure if its correct, but at least they look significantly different

DMA57361

hello

and the top one has an odd "backstep" :/ these dogs need to learn how to walk sensibly

Ivo Flipse

ah, all contacts were behind the LF paw

so the pattern starts without the LF paw :P

that's lame

ah well, its just to support the numbers above it

so unless the veterinarians come up with something better, this is how its going to be for now

DMA57361

f/e

but you're still making various progresses then?

Ivo Flipse

well I think I did this in 30 minutes

splitting up the results that is

so I'm fairly content with how fast that went

I needed to separate all results, into running and walking, so I can do some statistics on them

I'm suspecting there are some outliers, which need culling

DMA57361

btw, what's your next milestone? you have more meetings etc coming up?

Ivo Flipse

11:51 AM

@DMA57361 the clinic is waiting for their results T minus 1.5 months ago

and I've been procrastinating from tackling the results, though I'm now finally making some progress on that area

DMA57361

oic, so you're playing a little bit of catch-up now?

Ivo Flipse

probably going to a conference next week, where my old employer is one of the sponsors

@DMA57361 yeah, though making that .exe, cleaning up my displays, interpolating my results and such isn't wasted effort

I also fixed a slew of bugs

so that should save me time down the road

DMA57361

true, it's all progress in the right direction

Ivo Flipse

the messing I've done with Kronos his app has helped me with my refactoring skills

every time I need to add several items now, I'll try to make classes and simply make several instances of that

normally I wouldn't do that, because so many things are different between each item

now I just pass a bunch of arguments, to tweak all those settings :)

Hopefully the next step of progress is making a generic results page, that just adapts to the input, so I can easily display multiple variations of the same thing

like currently I have a display of the average contact + the axis (which sucks) + the center of pressure (which isn't aligned) + the toe regions (which is still my old version)

the logical next step is simply to turn displaying one of these layers/addons on/off to display them

but as long as the clinic doesn't show some more interest in doing a followup, I'm not particularly in a hurry to deliver the results

DMA57361

@IvoFlipse hmmm, so if the clinic is losing interest you have other leads or market you're aiming for?

Ivo Flipse

12:00 PM

@DMA57361 well in that case I'll have to lend money from my parents and/or make sure I can process human measurements. That way I can do a project for them, which off course they only do to support me, but allows me to continue working on it

hopefully if I split up all the results and come up with some basic stats for each dog

pass that to a spreadsheet or pdf to export, the clinic can do whatever the hell they want with the data

and then it should be enough features to start looking for some more clients

Speaking of the devil, I just got an email from the veterinarian who performed the measurements (though not in charge of things)

DMA57361

fair enough

@IvoFlipse oh?

Ivo Flipse

well she's just asking how long I expect it will take me to get her the results

DMA57361

oic, well, she can have them Soon™

Ivo Flipse

indeed

well I guess it would help if I installed a version of my app on one of their laptops

so that I only have to push a new update once I'm 'Done'

DMA57361

possibly

just be wary of ending up doing more support than development

Ivo Flipse

12:07 PM

@DMA57361 oh I don't give support, it works as is

so they'll have to wait with actually using it until I'm done

but they can have a look at the data in the mean time

DMA57361

right, but to look at the data they have to use the software...? which means setting it up, getting it working, showing them how to get to the data, etc?

Ivo Flipse

@DMA57361 That's the last thing I need to decide on, I need to pick a license to slap on my app

DMA57361

good point

Ivo Flipse

luckily when I make it into an .exe, they can't really touch the source unless they know how to open them

DMA57361

@IvoFlipse well... don't py2exe things just hide the source in a zip?

Ivo Flipse

12:10 PM

@DMA57361 It indeed means I have to install my app + MySQL and make sure they have all the data

@DMA57361 well the version that 'hides' everything didn't run, haven't figured out what the issue is yet

but still it packages the .pyd or pyc files, good luck with those as a non-programmer :P

DMA57361

@IvoFlipse hmmm, but still you can license it how you like

Ivo Flipse

@DMA57361 I was thinking about one of the GPL ones, since it still allows me to sell a license as well, but prohibits anyone from profiting directly from my work

DMA57361

@IvoFlipse indeed

Ivo Flipse

well I guess any license allows dual-licenses, but if someone wants to use my work, they'll have to come to some agreement with me

DMA57361

and there's nothing to stop you installing the pre-release version on something much more restrictive and then going GPL when you release

Ivo Flipse

12:13 PM

@DMA57361 the phd-er in London actually has a version with no license at all, but I'm going to try and lock down some of my updates in the future

just to be save

I don't want to hinder my users either, so its a delicate balance

DMA57361

@IvoFlipse if there's no license at all you might be implicitly covered by copyright... but that's a bit dangerous, maybe :/

Ivo Flipse

@DMA57361 well she 'promised' me she was using it safely

I just have to make sure she get's a version she can use more liberal

and if they want access to the source code (like she has), they'll simply have to do a project with me :)

DMA57361

the license for the pre-release doesn't have to impede usage, but could restrict distribution of the original or derived works.

Ivo Flipse

@DMA57361 lol that already sounds pretty legalese ;)

DMA57361

@IvoFlipse unfortunately all licensing sounds legalese..

KronoS

7:19 PM

hey @IvoFlipse I'm in for the rest of the day....

Ivo Flipse

ah nice

well I'll be around for several hours

KronoS

ok cool... I have to remotely push an update... I made one yesterday but aparently didn't push it... so now I have to remote it and push it

Ivo Flipse

I haven't changed anything

so you should be fine

KronoS

@IvoFlipse I know. It was me that made the change, but didn't push

Grrr... can't connect.. .maybe I'll just redo it...

Ivo Flipse

no, just force push

or you mean you can't remote login?

KronoS

7:23 PM

@IvoFlipse ya I can't...

KronoS

8:11 PM

ok back to work

Ivo Flipse

hehe, who said I stopped working

KronoS

I meant me... :P

Ivo Flipse

KronoS

ok so I think that I need some help... you free @IvoFlipse?

Ivo Flipse

I can help you

KronoS

8:16 PM

Sweet... so I've created a class in trasktrackercontroller

called weights... and it's supposed to calculate the weight of each task

Ivo Flipse

yes, I'm seeing it

KronoS

but I'm not exactly sure:
a) if I set it up right
b) how to implement it exactly

- as this needs to be run on EVERY button that has been activated EVERY time a button is activated

Ivo Flipse

Ok, so how it currently worked was: you pressed a bunch of buttons, when you pressed the button in the bar, it would collect the passed times for each button

so that's wrong

KronoS

my way is wrong or the way that it was originally done?

Ivo Flipse

my way

though it was just to show it could be done

KronoS

8:19 PM

whew ok...

@IvoFlipse right I figured that

Ivo Flipse

every button needs to report how long its active at the moment a button is pressed?

KronoS

well not exactly... so here's what we could do...

Ivo Flipse

class Weights():
    """
    Used to calculate the weights and weighted durations of the tasks
    """

    def __init__(self, weight, numtasks, prevtime, currenttime, starttime):

        # time difference between button presses
        self.deltat = currenttime - prevtime
        # duration of time that button has been on
        self.duration = currenttime - starttime
        # sum of the weights that have been calculated.  If this is the first 'event' then weight will be orginally 0 and new weight

@KronoS tell me, I'll shut it ;)

KronoS

have a 'global' timestamp that just updates everytime a button is pressed

but every button needs to 'update' it's weight

because it changes everytime a button is pressed

Ivo Flipse

@KronoS help me figure out what everything means

currenttime and prevtime are?

or rather what's prevtime?

KronoS

8:22 PM

current time is the time when a button is pressed

prev time is the time that the last button was pressed

Ivo Flipse

right, so that's really the start time

or that's a global thing

KronoS

start time is the time that the actual button was pressed

prev time is a global thing

deltat or delta 't' is simply the change in time from one button press to another

duration is the time that the button has been pressed thus far

weight is simply the previous weight (0 if this is the first press)

and sumweight is the sum of the previous weight, and the current weight

oh whoops there's an error in there...

just a sec

Ivo Flipse

@KronoS what is weight(1)?

KronoS

it's not a function, but a value... sorry for mistype

Ivo Flipse

I know, I meant how does weight change

KronoS

8:29 PM

ok I just sent a push with the fix...

Ivo Flipse

so we need to split these variables for global/shared ones and those that are unique to impressed buttons

KronoS

weight is itnitially zero

then when a button is pressed it's 1/(number of current tasks)

so first button pressed is 1/1

second is 1/2

third is 1/3

and so forth

Ivo Flipse

well 1 + 1/2?

KronoS

but since the buttons won't be pressed at the same time everytime we have to account for changes in time

no it'd be 0+1/2

then 1/2 + 1/3

Ivo Flipse

so weight is global too

KronoS

8:31 PM

(if the time intervals were exactly the same)

no... number of tasks open is a global thing

Ivo Flipse

the next button needs to know what the weight of the previous button was

KronoS

1/(number of tasks)

no the same button needs to know what the same button's previous weight was

Ivo Flipse

@KronoS right, so this get's evaluated per button

what is the result of this all going to be?

KronoS

correct

to calculate weight for that time interval we need to multiply the change in time from one button press to the other by 1/(number of buttons pressed)

to determine the ACTUAL weight of the button we need to take the previous weight and add the most recent calculated weight

to determine duration we need to take the duration the button has been pressed and multiply it by it's weight

does that all make sense @IvoFlipse ?

Ivo Flipse

one sec

KronoS

8:39 PM

ok

Ivo Flipse

> weight + (deltat*(1/numtasks)) ==> so what would a hypothetical result of this be?

silly question, but shouldn't every task just have one duration?

KronoS

so let's say that no buttons have been pressed

I press button 'one'

it's weight was zero

currently there are 1 task(s) running

therefore 1/1

so weight would be 1 + deltat*1/1

let's say that deltat = 1

so weight would be 1

not let's say that 1 time unit passes and I press button 'two'

weight of button two was zero

I then add 1/2 or 1 / (num of tasks)

I multiply delta t by 1/2 = 1/2

button 'one' prev weight was 1

I take deltat and multiply it by 1/2

--> 1/2

I take prev weight of 1 and add 1/2

--> 1.5

Ivo Flipse

what is deltat at this moment?

KronoS

I'm assuming deltat is 1

everytime, in this scenario

Ivo Flipse

that means you press a new button every second right?

KronoS

8:47 PM

yes in this case, but it's not that pretty everytime...

Ivo Flipse

btw its self.deltat not deltat

I might be dumb, but shouldn't the total time of a button be

KronoS

right sorry... didn't want to type 'self' a bunch of times

Ivo Flipse

time1 * weight1 + time2 * weight2 + time3 * weight3

my point being, every time a button is pressed, EVERY button calculates time * weight

where time is 0 if it was inactive

KronoS

Hmmmm... yes that's right....

Ivo Flipse

so every button keeps track of its own time, where new time get's added until you're done (assuming the button get's activated at some point)

all we need to share is how many buttons are active at one point in time

assuming the whole round runs within 1 second (within your margin of error)

what we should do is let every button sent a message to the controller

KronoS

8:53 PM

@IvoFlipse wait what?

Ivo Flipse

where we keep a dictionary with keys for every task and 'log' whether the button is true or false

KronoS

what if it's less than one second? are you saying it'll screw up?

Ivo Flipse

@KronoS A: that's stupid, you would be doing 2 tasks at the same time

but my point is concurrency, you first need to have a weight, before you can continue calculating

so every button needs to report if they're active or not before you can continue

oh wait no, that's not needed

my point is

we have this one dictionary that keeps track of all tasks being active

we could just use an int or a list, but with a dictionary you can track what button was active and such

KronoS

well a dictionary would be better

Ivo Flipse

ok, what we should do is add a function + attribute to tasktrackercontroller

KronoS

8:57 PM

but I don't know a thing about dictionaries, other than what I just looked up

Ivo Flipse

we call it: def updateweight(self, message):

KronoS

under which class?

my weights class?

Ivo Flipse

then the message should be -1 or 1, for when you a button is turned off (weight - 1) or on (weight + 1)

no the main class: TaskTrackerController

KronoS

ok that's what i thought and just did

Ivo Flipse

ok

so our button class (in tasktrackerpanel) should sent 2 messages

pub.sendMessage("ButtonClass.toggledbutton", -1/1)

to explain how pubsub works

when importing wx.lib.pubsub, we import Publisher as pub

this has 2 methods we use: sendMessage and subscribe (there may be more but I don't need them yet)

like I shared the link, we will have to update this at some point, but not now

you send a message by giving a string " "

KronoS

9:03 PM

but what is the message then?

where it goes?

Ivo Flipse

you decide what this will be, it can be anything as long as they are unique or they will override similar messages (perhaps not allowed)

pub.sendMessage("ButtonClass.toggledbutton", -1/1)

then you pass along your actual 'message', being the object you want to move elsewhere

KronoS

so I could very well do this: pub.sendMessage("HolyCrapItsIVO",-1/1)

if I wanted to?... like the message has nothing to do with other sections of the code

Ivo Flipse

the other method we use is pub.**subscribe**("message you're subscribed to", object your sending)

yup

I started using the standard of MainClass.function, because it allows me to backtrack where they came from

KronoS

you just use that syntax to keep track of what you're doing?

brb

Ivo Flipse

yeah and its predictable, because I know what the format SHOULD be

KronoS

9:07 PM

ok that makes sense then... but what if you have multiple message to the same function?

Ivo Flipse

the function can subscribe to as many messages as it wants to

and several functions can send the same message too

its like delivering mail

it makes 1 round, delivers to all subscribers and then quits

so all buttons sent one message: "ButtonClass.toggledbutton"

KronoS

so I can have two functions that send the same HolyCrapItsIVO message

Ivo Flipse

yup

KronoS

ok

Ivo Flipse

what's nice is that you don't necessarily have to tweak your message

thats also what the new style API with keywords is for, you can deliver different data with the same message by adding a keyword

KronoS

9:09 PM

ya thats really nice

Ivo Flipse

but we're not using that

also, I believe you NEED to use the same keyword everywhere, because pubsub compares all the subscribers + sendmessage pairs

hence I just use 'message' in each function

its useful to use the same thing everywhere, because it makes your code predictable/readable

KronoS

message being the "Class.function" ?

Ivo Flipse

no

def functioname(self, message): <-- this message

KronoS

oh got it.. ok

that makes sense as well

Ivo Flipse

@KronoS then message is an object, to get the object out of it you have to use message.data

KronoS

9:14 PM

ok so when I 'subscribe' to something i have to use message.data

Ivo Flipse

@KronoS yes, the subscribed function needs the message keyword in the def statement and message.data to use it

btw you can also sent empty messages, basically its a way to trigger functions elsewhere

we use that between the ribbon + mainframe + other functions

KronoS

oh wow... ok...

i think I get that

Ivo Flipse

ok

then this updateweight function will sent a message with the weight out to every instance of the Weight Class you made

KronoS

ok so I have a updateweight function that sends messages to the Weight class

The weight class calculates a new weight for the button and then....

what?

Ivo Flipse

well you need to create an instance of that Weight class for every button

OR

KronoS

9:26 PM

which I would do with the creation of each button... right?

Ivo Flipse

have a dictionary with all the variables it needs to keep track off

@KronoS well its in the controller, so whatever the panel does is the panel's business

a dictionary is a data structure where objects are stored based on a key:value basis

KronoS

but what if I want to create/edit new or old tasks...

which would be easier to implement in that case?

Ivo Flipse

a = { 'a' : 1, 'b' : 2, 3 : [1, 2, 3]}

@KronoS then we need to create that dictionary in a generic way and/or have keys added to the dictionary based on buttons created

KronoS

where 'a' and 'b' are labels and 1,2,3 are values?

Ivo Flipse

a b 3 are keys

KronoS

9:29 PM

ok so a dictionary is the way to go

Ivo Flipse

a 2 [1, 2, 3] are values

what we would do is store the tasks based on the name we use in the panel

{'Data Gathering':[ ],'Collaboration':[ ],,'Outputs':[ ],,'Documentation':[ ],}

either we let the ButtonClass.__init__ sent a message to add a key

KronoS

Oh... I see then...

Ivo Flipse

or we let the ButtonClass.toggledbutton sent along the name of the button

the latter is a 'lazy' approach, which only tries to calculate the times for buttons that have actually been pressed, so that's probably preferable

so that sends a message: [self.name, -1/1] or {'name':self.name, 'state':-1}

then in tasktrackercontroller we need to tweak your class

the first time a button is pressed, we want to calculate its 'adjusted time' (timediff * weight)

so when we get a message we check against the dictionary whether it has any keys with the given value

if not, create one, if so get the values from it

KronoS

ok so let me see if I got this... what we're going to do is create a dictionary that we'll parse info of task name and status and current weight to?

Ivo Flipse

yeah

but when the state == 1 (button is turned on)

it should fill starttime with time.time() (or whatever)

then when another button comes in and has that state

it should go to this button's values

compare if starttime <= time.time() (its older)

then calculate the weightduration and store that

and update starttime with time.time() (or currenttime)

when the button state is -1 or another button comes along, we simply rinse and repeat

KronoS

9:40 PM

so state 1 is active and state -1 is inactive?

lol

Ivo Flipse

because the -1 state is also used to adjust the weight

you can have it be 0 too, but then you need to write a loop to check against its value

now its just weight + state

KronoS

oh and -1 would make it 'negate' itself... literally

Ivo Flipse

indeed

KronoS

hey is this a dictionary?

self.timediff[message.data['name']] = {'userid':userid,
'tasktrackerid':tasktrackerid,
'taskname':message.data['name'],
'timediff':round(message.data['stop'] - message.data['start'])}

Ivo Flipse

though, it should only be applied AFTER calculating the time

yes

to create a new key with the {} you do: dictionary[keyname] = value

KronoS

9:46 PM

ok so first the dictionary needs to be created it sounds like...

Ivo Flipse

and dictionaries can contain anything

you just need to create an initial dictionary

self.timediff = {}

you just do that in the init of tasktrackercontroller