Re: about CAT
Carlos Carroll
more info if your problem persists.
1) > For min-cost-max-flow all-pairs, the graph file should be the same as that
> used by min-cost-max-flow subset. The difference is only "Input File Type"
> and "Input File". While "Generic Data" and a source-target file are used for
> subset, ">>>None Selected<<<" should be used for all-pairs. But it didn't
> work. I tried to select "Generic Data" and didn't provide Input File, it
> still didn't work.
Input Files (Type) will say "Generic Data" for an all-pairs analysis as well.
Command syntax shown in the Output tab should be similar to:
"C:\Program Files (x86)\Connectivity Analysis Toolkit\Network
Flow.exe" -mcft2 -t 8 -f 1 "c:\my.lgf" "c:\test.txt"
When you say "I tried to select "Generic Data" and didn't provide Input File, it
> still didn't work." please explain what error you are getting.
Note that MCF allpairs take a long time in the present version of the
CAT so is of limited use.
This is unlikely to change anytime soon.
2) > For current-flow subset, the graph file should be the same as that used by
> current-flow all-pairs. The difference is only "Input File Type" and "Input
> File". In the tutorial for current-flow all-pairs, "Generic Data" is used
> for "Input File Type" and do not provide Input File. Here for subset, the
> "Input File Type" is "Source and Target", and the "Input File" is a
> one-column text file (sourcetarget2.txt). But it still didn't work.
Note that sourcetarget2.txt must be selected twice, in both fields
below "input file type".
Command syntax shown in the Output tab should be similar to:
C:\Program Files (x86)\Connectivity Analysis
Toolkit\pythonflow\pythonflow.exe" -e -x "C:\sourcetarget2.txt" -y
"C:\sourcetarget2.txt" "C:\hab5cond.txt" "C:\ouput.txt"
It is likely you will get a message: "CAT ran out of memory. This
function is memory-intensive.
Please try again on a system with more available RAM or see manual for
information on alternative functions with lower memory requirements."
This is still a limitation of the SUBSET current flow function. We DO
plan to resolve this in the upcoming CAT release.
On Mon, Mar 5, 2012 at 6:23 PM, <Canra...@dse.vic.gov.au> wrote:
> Dear CAT developers,
>
> I am using CAT to do connectivity analysis. I have gone through the
> exercises in the tutorial, which include shortest-path subset and
> all-pairs, min-cost-max-flow subset, and current-flow all-pairs. There is no
> problem.
>
> But when I tried min-cost-max-flow all-pairs and current-flow subset, it
> seems something is wrong.
>
> For min-cost-max-flow all-pairs, the graph file should be the same as that
> used by min-cost-max-flow subset. The difference is only "Input File Type"
> and "Input File". While "Generic Data" and a source-target file are used for
> subset, ">>>None Selected<<<" should be used for all-pairs. But it didn't
> work. I tried to select "Generic Data" and didn't provide Input File, it
> still didn't work.
>
> For current-flow subset, the graph file should be the same as that used by
> current-flow all-pairs. The difference is only "Input File Type" and "Input
> File". In the tutorial for current-flow all-pairs, "Generic Data" is used
> for "Input File Type" and do not provide Input File. Here for subset, the
> "Input File Type" is "Source and Target", and the "Input File" is a
> one-column text file (sourcetarget2.txt). But it still didn't work.
>
> Could you please advise on this?
>
> Best regards.
>
> Canran Liu
>
> Notice:
> This email and any attachments may contain information that is personal,
> confidential,
> legally privileged and/or copyright. No part of it should be reproduced,
> adapted or communicated without the prior written consent of the copyright
> owner.
>
> It is the responsibility of the recipient to check for and remove viruses.
>
> If you have received this email in error, please notify the sender by return
> email, delete it from your system and destroy any copies. You are not
> authorised to use, communicate or rely on the information contained in this
> email.
>
> Please consider the environment before printing this email.
>
>
>
>
>
>