-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: DimensionMismatch #199
Comments
I see, thanks for pointing this out. Could you test this with the master
branch of Circuitscape too? It might be fixed there.
Best,
Ranjan Anantharaman
…On Mon, Oct 21, 2019 at 3:49 AM MarioInTaipei ***@***.***> wrote:
Hi,
I ran a relatively large file (11M connections between 3960000 nodes ) in
Circuitscape 5.5.4 and Circuitscape 4.0.5 using the same .ini file.
It works well in 4.0.5 generating 216764 entries in the
output_voltages.txt.
In 5.5.4 it generates the error: "tried to assign 3960001-element array to
216764×1 destination".
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#199?email_source=notifications&email_token=ACFOAQJZM54IW6WSD3S362LQPVNJTA5CNFSM4JCZPWA2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HTCZJ3Q>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACFOAQJZL67EBKOLFWOEIZ3QPVNJTANCNFSM4JCZPWAQ>
.
|
I tried the master branch and get the same error.
Best,
Mario
On Wed, 23 Oct 2019 01:45:12 +0800, Ranjan Anantharaman
<[email protected]> wrote:
… I see, thanks for pointing this out. Could you test this with the master
branch of Circuitscape too? It might be fixed there.
Best,
Ranjan Anantharaman
On Mon, Oct 21, 2019 at 3:49 AM MarioInTaipei ***@***.***>
wrote:
> Hi,
> I ran a relatively large file (11M connections between 3960000 nodes )
> in
> Circuitscape 5.5.4 and Circuitscape 4.0.5 using the same .ini file.
> It works well in 4.0.5 generating 216764 entries in the
> output_voltages.txt.
> In 5.5.4 it generates the error: "tried to assign 3960001-element array
> to
> 216764×1 destination".
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#199?>email_source=notifications&email_token=ACFOAQJZM54IW6WSD3S362LQPVNJTA5CNFSM4JCZPWA2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HTCZJ3Q>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ACFOAQJZL67EBKOLFWOEIZ3QPVNJTANCNFSM4JCZPWAQ>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Could you share your input files and the ini file? |
Hi, |
@MarioInTaipei I am able to reproduce this error, I'll come up with a fix soon. I see that you're using network mode? Could I ask you about your application and why you choose to use network mode instead of raster mode? |
Hi,
thank you for the update. We are using circuitscape to solve complex
networks that represent conductive pathways in materials and since these
are 3D (or even more complicated) we cannot discretize them into a raster.
Best regards,
Mario
…On Fri, 06 Dec 2019 11:06:34 +0800, Ranjan Anantharaman ***@***.***> wrote:
@MarioInTaipei I am able to reproduce this error, I'll come up with a
fix soon. I see that you're using network mode? Could I ask you about
your >application and why you choose to use network mode instead of
raster mode?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
That's fascinating. Any pointers to your work or papers would be fun to look at. |
We are currently in the process of submitting the paper and I will update
you as soon as it comes out.
…On Fri, 06 Dec 2019 13:05:10 +0800, Viral B. Shah ***@***.***> wrote:
That's fascinating. Any pointers to your work or papers would be fun to
look at.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@MarioInTaipei I am currently in the process of finishing up my semester (and all the associated exams), and I will be able to work on this a little before Christmas time. I hope this does not get in the way of you submitting your work. |
Hi,
no worries, getting this to work is only a bonus. Good luck with your
exams!
…On Tue, 10 Dec 2019 05:06:33 +0800, Ranjan Anantharaman ***@***.***> wrote:
@MarioInTaipei I am currently in the process of finishing up my semester
(and all the associated exams), and I will be able to work on this a
little before >Christmas time. I hope this does not get in the way of
you submitting your work.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@MarioInTaipei I have been working on a fix, and got the following outputs. Could you verify that these outputs look right and match Circuitscape 4? if so, I'll push this fix. output_voltages.txt Thanks! |
Hi,
the results are spot on except for one issue: The first element (1, 0)
should not be there since it makes the array one element too long and is
not the correct voltage for the first node (i.e. 2, 20.7) is. Also, the
format of the first column used to be integer (1) but now is float (1.0).
This is not a problem for our purpose but might cause problem with others?
So, even in the current form the fix is solving all our problems!
Thank you.
Best regards,
Mario
…On Wed, 08 Jan 2020 17:49:07 +0800, Ranjan Anantharaman ***@***.***> wrote:
@MarioInTaipei I have been working on a fix, and got the following
outputs. Could you verify that these outputs look right and match
Circuitscape 4? if >so, I'll push this fix.
output_voltages.txt
output_node_currents.txt
output_branch_currents.txt
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hi,
I ran a relatively large file (11M connections between 3960000 nodes ) in Circuitscape 5.5.4 and Circuitscape 4.0.5 using the same .ini file.
It works well in 4.0.5 generating 216764 entries in the output_voltages.txt.
In 5.5.4 it generates the error: "tried to assign 3960001-element array to 216764×1 destination".
The text was updated successfully, but these errors were encountered: