Yep. That’s what I did!
Good time to dip my toes back into the Julia language pool. I’ve had some complaints about Julia. Quite possibly due to my not understanding certain concepts. One thing I can give Julia credit for is pushing me to move to Python 3! Julia to me had strong similarities to Python. At the same time it was also very different. I figured if I can learn Julia I could certainly learn Python 3. Going to Python 3 from Python 2 is way easier than going to Julia.
If I look at Date Modified for my Julia programs it looks like I haven’t written any since August of 2020, so almost a year ago. I had made a Julia YouTube video back in May 2019 that had over 532 views. Pretty good for me. I took it offline quite a while ago because I thought it was no longer relevant because of more recent updates. Just for kicks I put it back online. I watched it and it still seems relevant. The video was using version 1.1.0.
Ran an old SQLite program I wrote. Required packages SQLite and DataFrames. When I first started playing with SQLite in Julia back in the day I had no idea what a dataframe was but thanks Python Pandas I now do. And that always helps.
There was also this odd magic statement I was using because I saw it somewhere that looked like this…
df=DBInterface.execute(db, sql) |> DataFrame
I didn’t understand it but it worked! I’d rather understand it first before using magic. So today, I googled “|>” and found that it like linux piping. Def “Applies a function to the preceding argument. This allows for easy function chaining.” So I found the following 2 statements do the same thing as the 1 magic statement…
So now that I understand, I can happily go back to using the single magic statement!
Title says it all!
I did a million record Cobol sort months ago. Here I am talking about getting the Cobol sort to work.
Saw no mention of timings on my log.
So found old Jobstream and reran today for timings.
Input 1 million 165 byte records
Output 1 million 60 byte records
Sorted by Last Name, First Name
Below is a cut & paste from the output jobstream.
SORT01 – STARTED – TIME=17.26.26
SORT01 – ENDED – TIME=17.26.39
So 13 seconds
Buried in this post I mention that I sorted 1 million records, and did some calculations using gnuCobol in less than 3 seconds. Now you would expect a native program to be faster than an emulated program. Still I like these comparisons. I think the old mainframe COBOL program performed respectively under the circumstances. No doubt running much faster on my desktop than on million dollar hardware…back in the day!
OK…and! What am I supposed to do with this WordPress message? I looked at it and I don’t care!!!!! If I click the X to close the message it just comes back the next time I want to edit this post. How about an option? Switch to the autosave or Ignore the autosave.
If I click View I get this…
So I have one option? Restore?
I mean there are ways around this but it seems an option choice would solve the problem.
I don’t usually have trouble coming up with some kind of project to work on for some reason I am now.
The one thing (KDE System Monitor) I always wanted starting in a specific virtual desktop was the one thing giving me trouble. It was always starting in virtual desktop 1. Everything else seemed to reopen where I shutdown the system.
Right click menu bar select More Actions. We are concerned with the following 2. Possibly only one was needed but after a lot of trial and error it worked so I’m not sure if both apply.
Configure Special Windows Settings
Configure Special Applications Settings
Here is the Configure Special Windows Settings window. The procedure/options for Configure Special Applications Settings seem the same. Notice the Virtual Desktop option. Also need to Add Property for Maximized Horizontally. Finally click Apply at the bottom. Don’t select Fullscreen (like I did) or you loose your menu bars and it won’t be simple to close or change back. I started pressing keys until finally <Alt><F3> brought me to a place where I could undo Fullscreen.
I guess I never noticed or looked. But Tk4- uses Hercules version 4. The main Hercules page says the current version is hercules-3.07-1. There is a version 4 manual available with an date of November 21, 2015.
HHC01413I Hercules version 4.00
HHC01414I (c) Copyright 1999-2012 by Roger Bowler, Jan Jaeger, and others
HHC01415I Built on Jun 23 2016 at 20:32:29
HHC01416I Build information:
HHC01417I Hercules for TK4- (64-bit Linux)
HHC01417I Modes: S/370 ESA/390 z/Arch
HHC01417I Max CPU Engines: 8
HHC01417I Using setresuid() for setting privileges
HHC01417I Using POSIX threads Threading Model
HHC01417I Using Error-Checking Mutex Locking Model
HHC01417I With Dynamic loading support
HHC01417I Using shared libraries
HHC01417I With External GUI support
HHC01417I With IPV6 support
HHC01417I With HTTP Server support
HHC01417I With sqrtl support
HHC01417I With SIGABEND handler
HHC01417I With CCKD BZIP2 support
HHC01417I With HET BZIP2 support
HHC01417I With ZLIB support
HHC01417I With Regular Expressions support
HHC01417I Without Object REXX support
HHC01417I Without Regina REXX support
HHC01417I With Automatic Operator support
HHC01417I With National Language Support
HHC01417I Machine dependent assists: cmpxchg1 cmpxchg4 cmpxchg8
HHC01417I Running on bill-MS-7B79 Linux-5.4.0-77-generic. #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021, x86_
In my experience, my system monitors always graph right to left. So first off the History option seems to be what I’m familiar with…except it starts graphing left to right then when it reaches the other end it switches right to left. What in the Twilight Zone is going on? Am I crazy?
Also the graph is real time. Why is it history? Well actually everything is history after the current time has passed, which happens immediately.
I mean when I was in school and I studied history…it was things in the distant past, not something that happened yesterday.