Are you sure I did some digging it seems to me like it has to do with the plugin… but I am not 100% certain just curious sure looks like a wisdom file that is used. And the plugin uses python more or less now like I said I’m not certain I will have to check the logs I just haven’t hooked in and checked out the settings you’ve suggested.
Note: post missing links and data related due to 2 link limit.
You sure it isn’t a wisdom file that is used by the plugin it sure looks similar?
https://help2.innovyze.com/infoworkswspro/Content/HTML/WS/r_Wisdom_file_format.htm
Look familiar? Just like the file we upload.
IDK I think this might be fixable via the plugin somehow.
Seems like python is being used and there is an error based in the realm of the plugin or the wisdom file if that is what is being used became corrupted possibly the End of file EOL data which seems to change and possibly provide verification of the file and the listings not certain but seems it may have happened. Possibly the constant hammering of adding stuff like a nut updated some stuff without the EOL data changing or something I’m not certain it is a wild guess. Maybe I’ll try to get it back up there again and see what happens.
The error “CRB Wisdom::load remote file not callable” in a large database context typically indicates that you’re trying to directly call a function that’s not a function, but rather a module, property, or other non-callable object. This usually happens when you’re using a framework or library that has a module with a load attribute, and you’re mistakenly trying to execute the module itself.
Here’s a breakdown of what’s likely happening and how to fix it:
Understanding the Error
- Module Object vs. Function:
In programming, a module is a collection of functions, classes, and variables. You can access the elements of a module using dot notation (e.g., module_name.function_name). Trying to call the module object directly (without using a function within it) results in the “not callable” error.
You’re probably trying to call the CRB Wisdom module itself, instead of one of its functions, particularly the load function according to the error message.
How to Fix It
- 1. Identify the Correct Function:
Determine which function within the CRB Wisdom module is responsible for loading remote files. It’s likely named load or something similar.
- 2. Use Dot Notation:
Make sure you are calling the correct function using dot notation. For example:
Python
# Assuming 'wisdom' is the CRB Wisdom module wisdom.load(some_argument)
Instead of:
Python
#Incorrect CRB Wisdom.load(some_argument)
You need to use the module name CRB Wisdom with the function name load
- Verify the Arguments: Check the documentation for the
CRB Wisdom module to see what arguments the load function expects. Make sure you are passing the correct arguments in the correct order.
Example
Let’s say you have a CRB Wisdom module with a function called load_remote_file. You’d call it like this:
Python
# Assuming 'wisdom' is the CRB Wisdom modulewisdom.load_remote_file(file_url, database_connection)
Troubleshooting
Ensure the CRB Wisdom module is correctly imported into your program. You might need to adjust the import statement if it’s not being recognized.
Double-check that there aren’t any variable names that might be shadowing the module or function name.
Refer to the [documentation for CRB Wisdom]
Use debugging tools to inspect the values of variables and the types of objects involved in the code. This will help pinpoint the exact line where the error is occurring.
It is also possible the file got corrupted or something while hammering a bunch of data on it or it didn’t update the EOL information correctly I’m not entirely sure.
The wisdom file might have been created with a different version of FFTW than the one you’re currently using. Ensure you are using the same version of FFTW that generated the wisdom file or, if possible, try re-generating the wisdom file with your current FFTW version, [as suggested on Stack Overflow]
The wisdom file may have been created for a different size or type of FFTW plan (e.g., different number of data points, different FFT type) than the plan you are currently trying to use. Make sure the wisdom file matches the configuration of your current FFTW plan, [as noted on Stack Overflow]
- Wisdom File Corruption:
The wisdom file itself could be corrupted or damaged. Try creating a new wisdom file by re-exporting the optimization information for your current FFTW plans, [as suggested on Stack Overflow]
Ensure the path to the wisdom file is correct and accessible to the program using FFTW.
- FFTW Configuration Issues:
The FFTW plan might have been created with different flags (e.g., FFTW_EXHAUSTIVE, FFTW_PATIENT) than the ones used when the wisdom file was created. Re-create the plan with the same flags and re-export the wisdom, [as mentioned on Stack Overflow]
If you’ve set a time limit for FFTW plan creation using fftw_set_timelimit(), it might prevent the wisdom file from being created properly or loaded. Disable or adjust this time limit, [as suggested on Stack Overflow]
