[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Help-glpk] [Fwd: Problem with GLPK when trying to find value functi
From: |
Robbie Morrison |
Subject: |
Re: [Help-glpk] [Fwd: Problem with GLPK when trying to find value functions] |
Date: |
Fri, 27 Jul 2012 06:09:50 +1200 |
User-agent: |
SquirrelMail/1.4.22 |
Hello Sergey
Your two emails are both below. I deleted some material
to shorten this message. Some comments interleaved too.
------------------------------------------------------------
To: Robbie Morrison <address@hidden>
Subject: Re: [Help-glpk] [Fwd: Problem with GLPK when trying to find
value functions]
Message-ID:
<address@hidden>
From: Sergey Kuznetsov <address@hidden>
Date: Thu, 26 Jul 2012 17:20:27 +0000
------------------------------------------------------------
> Hello again Robbie,
>
> Sorry, last time I didn't ran valgrind correctly. My
> binary called 'test' so it's probably ran /usr/bin/test
> But now I run my binary for sure and it works!!! I
> guess if I don't find bag in my code I will use
> valgrind. But I still want to find the bag just for
> self-learning. Again, thank you very much!
If you want to run local files, use: $ ./test
As for naming your binary "test" .. very descriptive!
> Sergey
>
> On Thu, Jul 26, 2012 at 5:07 PM, Sergey Kuznetsov <address@hidden>
wrote:
>
>> Hello Robbie,
>>
>> I ran my binary under valgrind, here is summary:
>> ==12805== HEAP SUMMARY:
>> ==12805== in use at exit: 0 bytes in 0 blocks
[snip]
------------------------------------------------------------
To: Robbie Morrison <address@hidden>
Subject: Re: [Help-glpk] [Fwd: Problem with GLPK when trying to find
value functions]
Message-ID:
<address@hidden>
From: Sergey Kuznetsov <address@hidden>
Date: Thu, 26 Jul 2012 17:07:33 +0000
------------------------------------------------------------
> Hello Robbie,
>
> I ran my binary under valgrind, here is summary:
> ==12805== HEAP SUMMARY:
> ==12805== in use at exit: 0 bytes in 0 blocks
[snip]
Actually it looked like a pointer went out of
scope, or some such, before GLPK had finished
with it.
>>One other thought: GLPK is not officially thread safe:
>>do you call GLPK concurrently?
>
> At first, I ran GLPK in omp parallel for, it didn't enough memory for big
> instances, that's why I'm using in a loop:
> for each right-hand side{
> call GLPK;
> store optimal value;
> }
Okay.
> Thanks,
>
> Sergey
>
> On Thu, Jul 26, 2012 at 4:41 PM, Robbie Morrison
<address@hidden>wrote:
>
>>
>> Hello Sergey
[snip]
Your project sounds interesting, good luck.
---
Robbie Morrison
PhD student -- policy-oriented energy system simulation
Technical University of Berlin (TU-Berlin), Germany
University email (redirected) : address@hidden
Webmail (preferred) : address@hidden
[from Webmail client]