My A6 had started feeling a little lazy in traffic, so I assumed an ECU tune was the obvious answer. While checking SUSTDI, I realized that the slow feeling was mostly connected to how the gearbox changed gears. That saved me from choosing an upgrade that would not directly address what bothered me.

Hi everyone, I have some data from BL6-2, and I am new with Python-based software... quick question, which software(s) do I need to install to view my data? Thanks to whomever can help me navigate this.

Hi everyone, I am a novice in SixPack so I hope the question is not covered somewhere else.

I would like to use some Ca k-edge XANES spectra of references from the literature to calculate SPOIL values in SixPack. I only have the Athena prj for those references. Starting from the Athena project I saved for each spectra the .xmu file, that I loaded into Samview as shown below. I can only see the spectra if I look at the muT2 plot type, but not in the other plot types. I saved the spectra in .avg format to be open in background removal, but the .avg file seems to be empity. How can I use the data from the Athena project into SixPack?

I am currently working with SixPack v 0.68.

Thanks in advance!

I got a new computer and had to re-install SMAK, the newer Anaconda has a version of setup tools incompatible seemingly (traceback yields an error in finding pkg_resources) - rolled back the setup tools using:pip install "setuptools<70" for setup 69.5.1 and then smak was able to start normally. The prior issues with numpy and pymca noted below seemed OK now, but of course be aware when installing there can be versioning incompatibilities...

Today I noticed with our student's new install of SMAK 3.0.9 (although this was also happening with my 3.0.8 version originally before I fixed my .cfg file) the defaultPyMCAConfig.cfg file has a line that causes peak fitting to crash when performing MCA peak-fitting. The error that comes back from SMAK is:

ValueError Exception in Tk callback

  Function: <bound method Main.testMCAfitdata of <__main__.Main object at 0x000002EAA3173370>> (type: <class 'method'>)

  Args: ()

Traceback (innermost last):

  File "C:\ProgramData\Miniconda3\envs\smakenv\lib\site-packages\Pmw\Pmw_2_1_1\lib\PmwBase.py", line 1761, in __call__

Hello Sam,

I am a graduate student at Chungbuk University in Korea. 

I am trying to use Sixpack for data analysis, but I am unable to find the manual on the Samware website, which is preventing me from using it properly. 

On the homepage, Sixpack's manual is  under construction. 

Could you please send me the manual or some information like a document about Sixpack?

Thank you.

Hello,

I'm noticing that as I process some XAS data, some mu files (which I've prepared by averaging scans in SamView and then correcting in the background removal module) can't be plotted correctly when they are opened in the PCA module. When multiple files are prepared identically, some are affected and others are not. Both the .mu and .xdi mu files are affected. The files contain full spectra and I can't see any obvious problems in the files.

Repeating the processing steps with the same raw data seems to result in an identical mu file that can't be plotted. I get the same problem with versions 1.4 and 1.5.6. I haven't tried another computer yet but I'm having the problem on the BL4-1 processing computer. I made sure there are no hyphens in my file names.

I'm attaching example files and an image of the failed plotting.

Thanks for any…

I recently did a fresh install of Anaconda3 and SMAK on a M1 Mac.

While my previous installation of Anaconda and SMAK proceeded exactly as described on the installation webpage, this time I came across some hurdles.

1. While I believe that I had installed my previous Anaconda3 for all users, the "/opt/anaconda3" direcoty was in my "User/opt/anaconda3" directory as described in the installation instructions on sams-xrays. Yet this new installation installed in "/opt/anaconda3". i.e. directly on the Macintosh HD, not in the user directory. I may be mistaken about my previous install, but it is worth noting that maybe something changed with the installation defaults. Anyway, this meant that my shortcut no longer worked and I had to edit for the new directory.
   

2. The command for creating the smakenv "conda create -n smakenv python==3.10" created the environment in the "osx-arm64" architecture. i.e. the Apple Silicon architecture. The previous architecture is "osx-64". Not…

Hi - another error for installation has been reported.

We should get this in the installer in release 3.10, but until then, a new version of PyMCA was released using numpy 2.0, which breaks SMAK. Once there is a more uniform use of numpy 2.0 across all dependencies, SMAK will upgrade to numpy2.0 as well, but for now, we have to stick to the old version.

If you run into a numpy error in pyMCA when running smak, please downgrade pyMCA for now:

“pip install pymca5==5.8.2”

PyMCA 5.8.2 will definitely work, and maybe up to 5.9.0....

Cheers!