Jump to content
Beckman Coulter User Forums


  • Posts

  • Joined

  • Last visited

1 Follower

Contact Methods

  • Website URL
  • ICQ

Profile Information

  • Gender
  • Location
    Indianapolis, IN

Recent Profile Visitors

41,385 profile views

Ernie's Achievements


Newbie (1/14)



  1. I apologize for the delayed response. You can use non-Tesla NVidia boards, but you have to pass the /CUDA command line switch to the software when it's started. Bear in mind that when you use a video board for computation that you're sharing the board's RAM. Kaluza won't use more than 4GB of RAM, so if your board has enough RAM for the display at your chosen settings and still has 4GB left over then there's no compromise. If there isn't 4GB of RAM left over, then the file size that Kaluza can use may be limited. You can use the About Box in the software to see if your CUDA board has been recognized. It's difficult to recommend a specific CPU or RAM configuration as needs vary. Kaluza scales very well with CPU cores, having more CPUs and more cores per CPU will help performance. However, once the software is already fast enough for a given need, there's no incremental benefit to adding more cores. From a RAM standpoint, Kaluza is currently a 32-bit application and so cannot address more than 4GB of RAM. If there's enough RAM for the OS and other applications, leaving at least 4GB for Kaluza then that will be sufficient. Note that if Kaluza is using a CUDA board for computations, then there's little incremental benefit to more workstation cores or RAM from a Kaluza perspective.
  2. One way to do it is to to right click on "This PC" in an Explorer window and choose "Properties" from the menu. Then click on "Advanced system settings". In the window that appears, click on the "Environment Variables" button. The window that appears should show settings for the TEMP and TMP locations, as well as a number of other things.
  3. For any decent computer, and it sounds like yours are, that shouldn't be a challenging data set. Is there the possibility that the computer is using a network drive for the TEMP folder location? (Kaluza makes temporary copies of files.)
  4. This error most frequently comes from using a different version of R than is specified. While it's possible to download the correct version, several of the necessary libraries won't work with the older version of R. We haven't found a way to specify to use the older library versions. We're looking for solutions currently; it may be necessary to release a new version of the R plugin.
  5. We'll look into it. We may need more information to track it down. I'll send you a private message if necessary.
  6. Administrator rights are required to copy the plugin to the program directory. Try running Kaluza as Administrator prior to installing the plugin.
  7. Kaluza can use the GPU of NVidia video boards, sharing that board with the display. This is not done by default primarily because of RAM. The board's memory is shard between Kaluza and the display. Unless you have a board with a lot of RAM, there may not be enough. The more displays you're running, the higher resolution they use, the greater the color depth you've chosen, the more RAM the video system will use. To allow Kaluza to do this, you need to pass the /CUDA command line parameter to the software. For test purposes, the easiest way to do this is to open a command prompt, change the directory to the Kaluza directory, and run: Kaluza.exe /CUDA If the about box shows that the video board is being used, if performance is acceptable, if there are no other issues, then you may want to set up an icon to avoid using the command prompt. You can't modify the default Kaluza program shortcut, so you need to make one specifically for this. The easiest way to do this is the find Kaluza.exe in Windows Explorer, and right-drag it to the desktop. You'll be presented with a menu, one option is "Create Shortcut Here". That will create a shortcut that you can use to start Kaluza, and the properties of that shortcut can be modified to add in the /CUDA option.
  8. I apologize for the delay in approving your post. If this is still a problem, can you provide your exact Kaluza version from the About box, and also what version of Windows you're using?
  9. Thanks for the explanation, that does make sense. Kaluza, for better or worse, has a very strict "never modify the listmode" rule. So when you adjust compensation what Kaluza does is to store your original listmode as well as information about how you want to view it, including any compensation adjustments. So your compensation values are saved; they're in the XML that accompanies the listmodes. It would be technically possible to pull the information out of the XML file but it's pretty complicated. Unless you have access to a talented programmer, the path of least work is probably to do what you're already doing for each file.
  10. See the user's manual (C10986AB) pages xxxvii & xxxviii. Maximum number of gates in a Boolean expression is 16, maximum number of plots on a sheet is 200. Remember, that it's not the number of terms you type into your Boolean expression that counts, it's the total number of terms required to resolve your expression. So if you have a singlets gate that feeds into a lymphs gate and everything derives from that, you've already used two of your sixteen
  11. This isn't currently a feature. Why do you want to do this? Would this be a one-off or is this something you want to do repeatedly?
  12. I apologize for the delay in approving your topic. Our forum system didn't notify me for some reason. The "Logicle" transformation that Kaluza has is the biexponential transform, the same one from the Parks and Moore paper that most other packages use. Kaluza differs in that it locks two of the four parameters to make it easier to use, but generally speaking it gives the same results.
  13. You can determine what technology is being used to calculate results by looking in the about box. That information is right at the top. If you have a K40, you shouldn't need the /CUDA parameter. If your K40 isn't in use, try updating to NVidia's latest drivers.
  14. Kaluza for Gallios is supposed to be used with the Kaluza for Gallios workstation which currently comes with Windows 7. There aren't any current plans that I can share to move it to Windows 10.
  15. Hi Michal, Could you give a more specific example of what you want to change and what workflow you're performing? Thanks, Ernie
  • Create New...