[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PetscViewerBinaryOpen getting stuck
- To: petsc-users@xxxxxxxxxxx
- Subject: Re: PetscViewerBinaryOpen getting stuck
- From: "Matthew Knepley" <knepley@xxxxxxxxx>
- Date: Sat, 8 Mar 2008 09:31:25 -0600
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=dwQLxyA/rlSD75WbmRbKNQzsE99d6FjZI+Z1uMdj+Ko=; b=MsORofoGaPkzLlLIv0l3Ha7G3Y9WKd+oz6YF0sDh36DRbpk5/iMPZWUz8MCkkcQePmlknMYfPB8BP2Br9BAf8z9UXrH3Gzb04+H21Eypqjam14ecNHDoktSZPWVtfyh4Jzavv4szX3o2SVzNfBezR/gCSQjLM7JxqRHjmQqNI8E=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RPYiUP9Bt4wkT9HwgN015qqrYBs6MZ3fHXxke/vRJgJnoZGY9BFCcWsRcadhQeQ1eC3ingArUAPMfb8bm87/oybux0fz3Xu/Z8m/aZGzjol4qjL5PMxNhiSBSljtLxCSoB925UG4n7M/8rnJfQEkHxUYqCG+gu96+oN34TsX+pA=
- In-reply-to: <4E2720C8-23CC-4E3B-B967-393FF025F42E@columbia.edu>
- References: <4E2720C8-23CC-4E3B-B967-393FF025F42E@columbia.edu>
- Reply-to: petsc-users@xxxxxxxxxxx
- Sender: owner-petsc-users@xxxxxxxxxxx
On Sat, Mar 8, 2008 at 12:00 AM, Gideon Simpson <GRS2103@xxxxxxxxxxxx> wrote:
> I have some code that wants to read in a previously binary dumped and
> gzipped matrix. The first time I run this code, it opens the file
> with PetscViewerBinaryOpen, loads the data into the matrix and
> processes as expected. However, if, for some reason, I want to
> execute it a second time, when it tries to open the file, it gets
> stuck. Investigating a bit, it seems to be that the first time it
1) Is this serial or parallel?
2) What do you mean by "gets stuck"?
3) Is there a small example which illustrates this?
I am looking at the code, and do not see an obvious error.
Thanks,
Matt
> runs, when it gunzips the file, it leaves the file in /tmp. If that
> file is still in this folder, it gets stuck. If I remove it from /
> tmp, the code executes without a problem, as it did the first time.
>
> Obviously, I could avoid using zipped files. Is this a bug (or a
> feature)? Is there an obvious way to clean up /tmp after the code
> executes?
>
> -gideon
>
>
--
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which
their experiments lead.
-- Norbert Wiener