public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Problem with grow.exe demo test file for SLEUTH Urban growth model
Date: Fri, 29 Jul 2022 21:01:56 +0200	[thread overview]
Message-ID: <267c6127-576d-0fab-45d8-43136e78e5bc@gmail.com> (raw)
In-Reply-To: <0578f142-0ca1-2407-81ca-ed402ba469e8@cs.umass.edu>

On 29.07.2022 05:30, Eliot Moss wrote:
> On 7/28/2022 11:20 PM, Krishnaveni K S wrote:
>> Dear Yano,
>> Thank you so much for the support.
>> I have use 64 bit download from cygwin and used the demo files for 
>> test run.
>> Haven't used 32 bit..
>> Can you please suggest how to solve this?
>>
>> With regards
>> Krishnaveni
> 
> What is grow?  Where is it coming from?  How was it compiled?
> 
> Cygwin has a huge number of packages; generally one installs a selection.
> Doing them all verges on craziness.  So what is "all the required packages"
> in this case?
> 
> I feel there's a lot you aren't telling us.  Is this some app from a
> third party?  They may not have packaged it well with Cygwin.
> 
> Presumably, you meant ./grow.exe, not ../grow.exe (unless you were in
> a subolder and rally wanted grow.exe from the parent folder).
> 
> Etc.
> 
> Hope this helps advanced the cause a bit ....   EM
> 

Hi Elliot,

with the help of Google I found that:

http://www.ncgia.ucsb.edu/projects/gig/Dnload/download.htm

is the source of the package and the SLEUTHGA.zip contains both code
and a Cygwin 64 bit binary depending only from the Cygwin dll
built in 2017

$ cygcheck ./grow.exe
d:\cyg_pub\tmp\SLEUTHGA\grow.exe
   D:\cygwin64\bin\cygwin1.dll
     C:\WINDOWS\system32\KERNEL32.dll
       C:\WINDOWS\system32\ntdll.dll
       C:\WINDOWS\system32\KERNELBASE.dll^

The README point to a demo script in the Scenarios directory

$ cat Scenarios/doit
date > Andijan2_1991_55_100_0.13_900_55_50
../grow.exe evolve scenario.Andijan2_calibrate 55 100 0.13 900 55 50 >> 
Andijan2_1991_55_100_0.13_900_55_50
date >> Andijan2_1991_55_100_0.13_900_55_50

For what I can see running the script take almost 100% of one CPU but 
does not produce any error

   bash doit

(still running for the time being)

Krishnaveni,
are you running a different Scenarion ?

Regards
Marco





  reply	other threads:[~2022-07-29 19:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 21:00 Krishnaveni K S
2022-07-29  0:20 ` Takashi Yano
2022-07-29  3:20   ` Krishnaveni K S
2022-07-29  3:29     ` Takashi Yano
2022-07-29  3:30     ` Eliot Moss
2022-07-29 19:01       ` Marco Atzeri [this message]
     [not found] <104898279.297262.1659119846645@kpc.webmail.kpnmail.nl>
     [not found] ` <CAEv0NddY3cw-k8Z2v-oKh2x_dfGf8fAxbY=_un=giUBeJGsz=g@mail.gmail.com>
2022-07-29 22:57   ` Takashi Yano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=267c6127-576d-0fab-45d8-43136e78e5bc@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).