Tools for converting scientific software from IDL to Python
openai
To get started, install the latest openai library:
pip install openaithen set your OPENAI_API_KEY environment variable.
This code uses the gpt-3.5-turbo model; see:
For pricing information (as of March 2023, the cost is $0.002 / 1K tokens)
To convert some code to Python, simply call the topython.convert function with the code to convert as the argument:
from topython import convert
output = convert('/path/to/idl/file/my_code.pro')By default, the convert function works on a .pro file; to submit raw code instead of a file, set the raw keyword to True.
raw: set toTrueif the input is code in a string instead of a file
Starting with the input:
pro create_tplot_variable, name, suffix=suffix
if undefined(suffix) then suffix = '_out'
get_data, name, data=d
store_data, name + suffix, data={x: d.x, y: d.y}
endand using:
from topython import convert
output = convert(input, raw=True)We get:
def create_tplot_variable(name, suffix='_out'):
"""
This function does something useful
Parameters
----------
name : str
name of the variable
suffix : str
suffix to add to the name of the variable [default: '_out']
Returns
--------
"""
d = get_data(name)
store_data(name + suffix, data={'x': d.times, 'y': d.y})Note: this is the raw output from the function, nothing was added or changed.
Not only does it produce correct code - it includes a header, even though there wasn't one in the input! This is because we showed the model an example of a header prior to requesting the conversion.
To turn off the header, use the header option:
output = convert(input, raw=True, header=False)We now get:
def create_tplot_variable(name, suffix=None):
if suffix is None:
suffix = '_out'
d = get_data(name)
store_data(name + suffix, data={'x': d.times, 'y': d.y})Now for the magic - changing our input to:
; function that uses get_data to return the data for an input variable,
; and store_data to save the data with a suffixand again using:
output = convert(input, raw=True, header=False)We get:
def get_and_store_data(variable, suffix):
data = get_data(variable)
if data is not None:
store_data(variable + suffix, data={'x': data.times, 'y': data.y})
get_and_store_data('variable', '_suffix')
get_and_store_data('variable2', '_suffix')🤯 🤯 🤯
We can modify the input slightly to ask for a docstring:
; function that uses get_data to return the data for an input variable,
; and store_data to save the data with a suffix, with a docstringand again using:
output = convert(input, raw=True, header=False)We get:
def get_and_store_data(variable, suffix):
"""
Get the data for a variable and store it with a suffix.
Parameters
----------
variable : str
The variable to get the data for.
suffix : str
The suffix to add to the variable name when storing the data.
Returns
-------
data : dict
The data for the variable.
"""
data = get_data(variable)
if data is not None:
store_data(variable + suffix, data={'x': data.times, 'y': data.y})
return dataThe only problem is in the 'Returns' section of the docstring: get_data returns a named tuple, not a dictionary. We usually return the name of the variable created, so we can change our IDL comment slightly ask for that:
; function that uses get_data to return the data for an input variable,
; and store_data to save the data with a suffix, with a docstring,
; that returns the output variable nameThis returns a working function, with a correct docstring:
def get_and_store_data(variable, suffix):
"""
Get data for a variable and store it with a suffix.
Parameters
----------
variable : str
The variable to get data for.
suffix : str
The suffix to add to the variable name when storing the data.
Returns
-------
str
The name of the variable that the data was stored in.
"""
data = get_data(variable)
if data is not None:
store_data(variable + suffix, data={'x': data.times, 'y': data.y})
return variable + suffix- The upper limit seems to be around 200 lines per function/procedure (depending on line density), or around 10KB
- Due to the caveat above, when converting files with multiple proceudres or functions, the
convertroutine will attempt to split the file up into individual functions, and send each one to the model independently. This splitting is based on 'end's in the IDL code, so if your functions include 'end's that aren't proper procedure/function 'end's (e.g., if you use 'end' to end an 'if' statement instead of 'endif'), you'll get some bad results; exception: 'end's that exist inside 'case' statements should be fine.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent