Skip to main content

How to do an already doomed test

Read this blog MS Office 2007 versus Open Office 2.2 shootout. The test was already flawed from the beginning for the following reasons:

  • The author did not upload the original file which is probably a Excel 97 xsl file as a reference

  • Instead, two different formats were used: one from OpenOffice 2.0 beta sxw which is a compressed file and other a xml file from Microsoft Office 2003.

  • Since two different formats were used, the test is automatically void of meaning because of the lack of the original file.

  • Renaming the xml file to xsl like the author, I verified if it can be read with OpenOffice 2.2. It does not because the data is interpreted as xml which will exceed the limit of row in Calc application. Office Excel 2003 will render like a spreadsheet due to proprietary XML parser. However, Excel 2003 cannot read sxc nor OpendDocument Spreadsheet unless SUN's Open Document Format plugin is used.

  • The test is unrealistic in real world business because of the size (273 Mib of spreadsheet data). According to the author, the spreadsheet is actually a log file. One has to wonder why using a spreadsheet application to archive log.


Smooge said…
As horrible as it sounds.. I have regularly seen 100+ MB excel spreadsheets with log data and other stuff in it.

Remember to look at the problem from a Windows users perspective. You have large amounts of data you want tabulated, and you have a very limited amount of tools to do it with. You can import the file into word, but it wont be able to correlate all the events together. So you import it into excel and have a column for time, for type of events, and data. Tada, now you can use a tool you are familiar with to manipulate the log data. (and you can use things like normalization etc if you need statistics). Is it optimal.. no.. but it is a matter of what tools you know. [I mean how many perl/awk/python programs do exactly the same thing because each specific author knew what one tool to write it with.]

Popular posts from this blog

Using AMD RX Vega driver OpenCL on Fedora 29

The Raven Ridge APU is very capable processor to handle OpenCL inside some applications like Blender, Darktable and Gimp. Unfortunately, the current implementation from Mesa, clover, stuck to 1.3, is not supported. AMD released their driver 18.40 with OpenCL2.0+ targeting only Red Hat Enterprise Linux/Cent OS 6.10 and 7.5 in addition of Ubuntu LTS. The good new is the former rpm format can be used on Fedora.

The graphical part of Raven Ridge is Vega 8, basically a cut-down of Vega56 or Vega64 meaning choosing either driver for RX Vega.
The instruction is provided for extracting the rpm files but here is
 some requirements for OpenCL:
kernel-devel (provided by Fedora repository)amdgpu-dkmsdkmslibopencl-amdgpu-proopencl-amdgpu-pro-icd Once done, applications needing OpenCL will automatically detect the driver located on /opt/amdgpu/lib64. Blender will list as unknown AMD GPU and Darktable will enable it.

There is a ROCm version but it currently does not support the graphical side of Rav…

Improving HP Envy x360 convertible on Linux: the missing accelerometer driver

If you own an HP laptop equipped with AMD processor, you may find out the auto-rotation will not work as intended. It turned out that sensor is missing a driver not currently available on Linux kernel using the lspci -nn command from the terminal

03:00.7 Non-VGA unclassified device [0000]: Advanced Micro Devices, Inc. [AMD] Device [1022:15e4] That driver in question is AMD Sensor Fusion HUB. Unfortunately, researching it turned out harder even on AMD own website. Bug is already filed without answer yet from one of AMD representative.

Detailing the installation of AMD OpenCL rpm for Fedora

Revisiting the previous blog and freshly reinstalling Fedora Design Suite due to a busted boot, I look at the official guideline from AMD Driver for Red Hat Enterprise Linux 7.2 and write a way to improve the process of installing on Fedora 29 in this example.

Extracting the tarball contains the following:
amdgpu-installamdgpu-pro-install symlink to amdgpudoc folderrepodata folderRPMS folder containing rpm package
Executing the command ./amdgpu-install -opencl=pal --headless sadly failed on Fedora on that line:

./amdgpu-install -y --opencl=pal --headless
Last metadata expiration check: 0:30:51 ago on Mon 19 Nov 2018 07:13:43 PM PST.
No match for argument: amdgpu

Upon closer look, the script failed to created a temporary repository on /var/opt/amdgpu-pro-local probably explaining why amdgpu metapackage name failed to display. Someone should investigate and provide a fix. At least, we find out Fedora support is available but unofficial.

Due to its design, Gnome Software only allows one cli…