I tried to write a fortran code where arrays were declared using 2D fortran syntax and then write a quadmesh and material object. I ran into problems between noncollinear and collinear cases. Its very peculiar and noninutitve. It no doubt has to do with rowmajor vs. colmajor storage orderings. But, getting both cases to work correctly is totally counter-intuitive. It makes me think that there may be a number of funky issues in using the fortran interface for real 2D arrays (probably only relevant to quad objects). I've attached copy of the fortran code here
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 2428
Status: New
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: array ordering issues in fortran interface
Assigned to: -
Category: -
Target version: -
Author: Mark Miller
Start: 10/24/2015
Due date:
% Done: 0%
Estimated time:
Created: 10/24/2015 03:37 pm
Updated:
Likelihood: 3 - Occasional
Severity: 2 - Minor Irritation
Found in version: 4.8
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
I tried to write a fortran code where arrays were declared using 2D fortran syntax and then write a quadmesh and material object. I ran into problems between noncollinear and collinear cases. Its very peculiar and noninutitve. It no doubt has to do with rowmajor vs. colmajor storage orderings. But, getting both cases to work correctly is totally counter-intuitive. It makes me think that there may be a number of funky issues in using the fortran interface for real 2D arrays (probably only relevant to quad objects). I've attached copy of the fortran code here
griffin28
commented
5 years ago
I tried to write a fortran code where arrays were declared using 2D fortran syntax and then write a quadmesh and material object. I ran into problems between noncollinear and collinear cases. Its very peculiar and noninutitve. It no doubt has to do with rowmajor vs. colmajor storage orderings. But, getting both cases to work correctly is totally counter-intuitive. It makes me think that there may be a number of funky issues in using the fortran interface for real 2D arrays (probably only relevant to quad objects). I've attached copy of the fortran code here
-----------------------REDMINE MIGRATION----------------------- This ticket was migrated from Redmine. As such, not all information was able to be captured in the transition. Below is a complete record of the original redmine ticket.
Ticket number: 2428 Status: New Project: VisIt Tracker: Bug Priority: Normal Subject: array ordering issues in fortran interface Assigned to: - Category: - Target version: - Author: Mark Miller Start: 10/24/2015 Due date: % Done: 0% Estimated time: Created: 10/24/2015 03:37 pm Updated: Likelihood: 3 - Occasional Severity: 2 - Minor Irritation Found in version: 4.8 Impact: Expected Use: OS: All Support Group: Any Description: I tried to write a fortran code where arrays were declared using 2D fortran syntax and then write a quadmesh and material object. I ran into problems between noncollinear and collinear cases. Its very peculiar and noninutitve. It no doubt has to do with rowmajor vs. colmajor storage orderings. But, getting both cases to work correctly is totally counter-intuitive. It makes me think that there may be a number of funky issues in using the fortran interface for real 2D arrays (probably only relevant to quad objects). I've attached copy of the fortran code here
Comments: