call_py_fort icon indicating copy to clipboard operation
call_py_fort copied to clipboard

Call python from fortran

Results 8 call_py_fort issues
Sort by recently updated
recently updated
newest added

I'm trying to pass an array between Fortran and Python but the dimensions and type are not matched. In Fortran I have ```fortran (gdb) ptype tgrnd type = real(kind=8) (2,72,0:47)...

LHS should be RHS?

This PR is a start at addressing #20. It moves the setting of the C and fortran compilers within the if blocks and addresses a typo in the specification of...

Currently the C and fortran compilers are hardcoded to be `gcc` and `gfortran`: https://github.com/nbren12/call_py_fort/blob/04ed7910457492759c69e457d22e53eaf30b385d/CMakeLists.txt#L8-L9 This interferes with building on systems that use different compilers. The solution is probably to have...

how we can use values of few variables into python. For example, in Fortran, I am running a calculation for calculation of few coordinates. That coordinate values I have to...

enhancement

The module, package, and library names should be consistent. Currently the module is named `callpy_mod`, the package is `call_py_fort`, and the library is `callpy`.

Currently set_state only supports arrays, which is inconvenient.

The libraries should be renamed to be more specific to this package. Maybe `-lcallpy_python` and `-lcallpy_fortran` would be good.