Eric, That worked - I had, in fact, neglected to update the base library. Now, after the second run of je_update_jpacman_'' I get -
9!:14'' j901/j64avx/darwin/beta-h/commercial/www.jsoftware.com/2019-08-26T15:19:32 and the impressive timing improvements came back. Maybe including a specific first step of: 'update' jpkg 'base library' would have gotten me going without all the noise. This is indeed a MUCH handier way to upgrade releases! Good work! Thanks for your patience! - joey > On 2019Aug 27, at 11:24, Eric Iverson <[email protected]> wrote: > > Joeh, > Just noticed that the je_update_pacman_ result you report is from the old > version. > > First you need to do an update to the base library. This will get you the > new version of je_update and then you might get the new avx version > installed. > > 1. update base library > 2. je_update_jpacman_'' NB. this may just get you a version that supporte > 2!:7 > 3. je_update_jpacman_'' NB. 2nd time will use 2!:7 result to get the best > version for you > > > On Tue, Aug 27, 2019 at 2:02 PM Joey K Tuttle <[email protected]> wrote: > >> Here is the result of running things again - >> >> MBpro-3:Downloads jkt$ jb >> 2!:7'' >> avx avx2 >> JVERSION >> Engine: j901/j64/darwin >> Beta-h: commercial/2019-08-26T15:18:27 >> Library: 9.01.06 >> Platform: Darwin 64 >> Installer: J901 install >> InstallPath: /applications/j901 >> Contact: www.jsoftware.com >> 9!:14'' >> j901/j64/darwin/beta-h/commercial/www.jsoftware.com/2019-08-26T15:18:27 >> load'pacman' >> je_update_jpacman_'' >> http://www.jsoftware.com/download/jengine/j901-beta/darwin/j64/libj.dylib >> saved as: ~temp/je_update/libj.dylib.new >> new version: j901/j64/darwin/beta-h/commercial/ >> www.jsoftware.com/2019-08-26T15:18:27 >> the current JE is already up to date >> exit 0 >> >> >> MBpro-3:Downloads jkt$ jb >> 9!:14'' >> j901/j64/darwin/beta-h/commercial/www.jsoftware.com/2019-08-26T15:18:27 >> 2!:7'' >> avx avx2 >> timex '%. 1000 1000 ?@$0' >> 0.695231 69208384 >> exit 0 >> >> >> MBpro-3:Downloads jkt$ ja >> 9!:14'' >> j807/j64/darwin/release-d/commercial/www.jsoftware.com/2019-03-18T16:07:14 >> 2!:7'' >> |domain error >> | 2!:7'' >> timex '%. 1000 1000 ?@$0' >> 0.407537 69208384 >> NB. same as time reported by beta-g... >> exit 0 >> MBpro-3:Downloads jkt$ >> >> So, no joy here. I agree with Pascal that it would be nice AVX etc was >> mentioned if in fact it was being used. >> >> - joey >> >>> On 2019Aug 27, at 10:49, Eric Iverson <[email protected]> wrote: >>> >>> Joey, Pascal, >>> Sounds like you are not getting the avx version. >>> >>> Check the result of 9!:14'' or JVERSION. It should indicate avx, if not >>> then you are not running the avx version. >>> >>> The 2!:7'' result should indicated the versions your hardware can run. >>> >>> You may just need to do the install again so that the 2!:7 result can let >>> it get the avx version. >>> >>> Please: >>> load'pacman' >>> je_update_jpacman_'' >>> >>> Restart and check 9!;14'' >>> >>> If this works, then it means my initial instructions that tried to say >>> doing the update 2 times would be necessary from older installs. >>> >>> >>> >>> >>> On Tue, Aug 27, 2019 at 1:08 PM Joey K Tuttle <[email protected]> wrote: >>> >>>> Eric, >>>> >>>> I'm befuddled by the NOTE: in your announcement. The install j901 beta-h >>>> went fine, I assumed you intended '' instead of a single ' ... >>>> >>>> But, when I did my usual benchmark, it took twice as long as the version >>>> (beta-g) that was replaced. Then I reread your note and ran it again >> (with >>>> no change in timing results). >>>> >>>> Looking at https://code.jsoftware.com/wiki/System/Installation/Zips I >>>> don't see any indication that there are different versions available. I >>>> applaud the intent that "An initial install JE will run on all hardware >> and >>>> does not require advance hardware." However, that seems to conflict with >>>> the statement on the Zips page where it says, "J901 is available only in >>>> J64 AVX versions" >>>> >>>> What am I missing? How can I get the zippy AVX version running on my Mac >>>> (without regressing to j807)? >>>> >>>> - joey >>>> >>>>> On 2019Aug 26, at 15:37, Eric Iverson <[email protected]> >> wrote: >>>>> >>>>> Improvements in this release allow it to be automatically installed >> into >>>> an >>>>> existing j901 install (no need to run a command script). >>>>> >>>>> First step is to install latest base library with pacman and then >>>> restart. >>>>> >>>>> JE naming conventions change in beta-h. An install contains a single JE >>>>> (e.g., j.dll). An initial install JE will run on all hardware and does >>>> not >>>>> require advance hardware. Update checks hardware capabilties and >>>> downloads >>>>> an appropriate advanced hardware version if available. For example, >>>>> hardware check could indicate avx is supported, so update would >> download >>>>> the latest javx.dll, which would then renamed to j.dll in the install >>>>> folder. >>>>> >>>>> Install the j901 beta-h: >>>>> >>>>> start J: >>>>> load'pacman' >>>>> je_update_jpacman_' >>>>> >>>>> An available advanced hardware or newer beta version JE will be >>>> installed. >>>>> Restart J to run the new JE and check JVERSION. >>>>> >>>>> NOTE: Older j901 installs don't support the query for hardware >>>>> capabilities. In this case update will install the new beta version >>>>> (without advanced hardware support) as it can't be sure what version >> will >>>>> work. Running update again will get the appropriate advanced hardware >>>>> version. >>>>> ---------------------------------------------------------------------- >>>>> For information about J forums see http://www.jsoftware.com/forums.htm >>>> >>>> ---------------------------------------------------------------------- >>>> For information about J forums see http://www.jsoftware.com/forums.htm >>>> >>> ---------------------------------------------------------------------- >>> For information about J forums see http://www.jsoftware.com/forums.htm >> >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
