search for: i100

...tently ordered interaction terms. There are abviously several work arounds. ### Start of example dfr <- expand.grid(i=0:154,j=0:154) dfr <- dfr[with(dfr,i+j<=154),] dfr$logj <- with(dfr,log(j+0.5)) dfr$jmin6 <- with(dfr, pmin(j,6)) dfr$ihalf <- with(dfr, factor(floor(i/6))) dfr$i100 <- with(dfr, ifelse(i<100,1,0)) dfr$j0 <- with(dfr, ifelse(j==0,1,0)) Ai <- runif(length(levels(dfr$ihalf))) Ai <- Ai-Ai[1] Bi <- runif(length(levels(dfr$ihalf))) Bi <- (Bi-Bi[1])/10 eta <- with(dfr, -5 -2.5*logj - 3*i100*j0 + 0.01*jmin6+Ai[as.numeric(ihalf)]...

...t do not register allocate them (through the definition of > allocation_order_end()). > > -Chris Hope I understand you correctly: def C0 : ConstFpReg<0, "c0">; ... def C200 : ConstFpReg<199, "c200">; def I0 : ConstIntReg<0, "i0">; ... def I100 : ConstIntReg<100, "i100">; def R0 : TempReg<0, "r0">; def R32 : TempReg<31, "r32">; def V0 : InputReg<0, "v0">; .. def V10 : InputReg<9, "v10">; def O0 : OutputReg<0, "o0">; .. def O4 : OutputReg<...

2014-02-13 6:55 GMT+01:00 Alf H?gemark <alf at i100.no>: > Hi > Hi Alf, > On > http://nutwiki.kanonbra.com/wiki/Category:Eaton_Powerware_5110 cool thing! But duplicating the NUT Device Dumps Library [1]. The DDL can also serve both users and developers purposes, by providing these dumps as .dev files (usable with dummy-ups). I...

On 08/07/2013 02:02 PM, Bendtsen, Jon wrote: > On 07/08/2013, at 13.40, Jan Phillip Greimann <jg at softjury.de> wrote: > >> Hi there, >> >> OS: (L)ubuntu 12.04 precise LTS >> Nut: 2.6.3-1ubuntu1.1 >> Installation Method: Package (apt-get install nut) >> Hardware: HP R1500 G3 INT > > FYI: > I have a different UPS, a HP R3000 XR and I monitor

Hi On http://nutwiki.kanonbra.com/wiki/Category:Eaton_Powerware_5110 you can see what is reported. The unreleased part refers to v2.7.1, which is now released. Alf Greg Vickers <daehenoc at iinet.net.au>: >Hi all, > >I've hooked up an Eaton Powerware 5110 to Ubuntu 13.10 server, and >configured nut appropriately. The cgi scripts are working fine, but on

On Sat, 23 Jul 2005, Tzu-Chien Chiu wrote: > 2005/7/23, Chris Lattner <sabre at nondot.org>: >> What does a 'read only' register mean? Is it a constant (e.g. returns >> 1.0)? Otherwise, how can it be a useful value? > > Yes, it's a constant register. > > Because the instruction cannot contain an immediate value, a constant > value may be stored in

2005/7/23, Chris Lattner <sabre at nondot.org>: > > What does a 'read only' register mean? Is it a constant (e.g. returns > 1.0)? Otherwise, how can it be a useful value? Yes, it's a constant register. Because the instruction cannot contain an immediate value, a constant value may be stored in a constant register, and it's defined _before_ the program starts by

=?ISO-8859-1?Q?Alf_H=F8gemark?= <alf at i100.no> writes: > I am working on improving the bcmxcp driver, to add more data reported > from the driver, and also add support for sending more commands to the ups. > The code changes are currently not part of any release, but they are in > github, and some more are on the way. >...

2014-02-16 8:31 GMT+01:00 <alf at i100.no>: > Hi > Hi Alf, > One idea I've had for some time, but unfortunately not had time to > implement, is to add a general SNMP agent, which will work with all UPSes > supported by nut. > The idea is to have the SNMP agent use the "nut API" to fetch values from...

Hi All, I am using PWLIB-1.6.6-1 and Openh323 1.13.5-1 and running a RH7.3 machine and I am unable to compile asterisk due to these errors. say.c: In function `powiedz': say.c:1633: parse error before `int' say.c:1636: `i1000E6' undeclared (first use in this function) say.c:1636: (Each undeclared identifier is reported only once say.c:1636: for each function it appears in.) say.c:1638: parse error before `int' say.c:1641: `i1000E3' undeclared (first use in this function) say.c:1643: parse error before `int&...

On 08/08/2013, at 18.58, Alf H?gemark <alf at i100.no> wrote: > On 08/07/2013 02:02 PM, Bendtsen, Jon wrote: >> On 07/08/2013, at 13.40, Jan Phillip Greimann <jg at softjury.de> wrote: >> >>> Hi there, >>> >>> OS: (L)ubuntu 12.04 precise LTS >>> Nut: 2.6.3-1ubuntu1.1 >>> Instal...

hem, in the hurry of sending, I've forgotten a link... 2014-02-18 22:45 GMT+01:00 Arnaud Quette <aquette.dev at gmail.com>: > > > 2014-02-16 8:31 GMT+01:00 <alf at i100.no>: > (...) > > That made me realize that it's still not referenced on the NUT Related > Projects page. > (yup Charles, yet another unshared thing...) > This last point is now fixed: > https://github.com/networkupstools/nut-website/commit/6d503c1c7e9f235263927ee2186ae3...

Hi One idea I&#39;ve had for some time, but unfortunately not had time to implement, is to add a general SNMP agent, which will work with all UPSes supported by nut. The idea is to have the SNMP agent use the "nut API" to fetch values from the UPS. So the SNMP agent will be similar to the "upsc" utility. Whenever the SNMP agent is queried for information, it will use the

On Feb 15, 2014, at 12:54 PM, Arnaud Quette wrote: > 2014-02-13 6:55 GMT+01:00 Alf H?gemark <alf at i100.no>: >> Hi > > Hi Alf, > >> On >> http://nutwiki.kanonbra.com/wiki/Category:Eaton_Powerware_5110 > > cool thing! > But duplicating the NUT Device Dumps Library [1]. > The DDL can also serve both users and developers purposes, by providing these dumps as...

...scern the state or future direction of IAX on the SNOM100. The most recent image appears to be from September 2002. There was a message on this list stating that SNOM was coming to visit Digium last April with the intention of adding IAX support themselves. For a while there was reference to the I100E on the asterisk and/or digium web sites, but this is gone now I think. This was apparently a rebadged SNOM 100 w/ IAX. Can anyone fill me in on what I'm missing? Does the 0923 SNOM IAX image do IAX2? In general, what's the status of this software, and how does the 0923 image work? Many...

Hi Here is a very minor patch for the bcmxcp.c driver, mainly fixing the function name used in debug statement, and at the same time fix indentation. Regards Alf Hogemark From 86c7940d0ea11b5b38a7f4518095ee2428d658c7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alf=20H=C3=B8gemark?= <alf at i100.no> Date: Mon, 1 Jul 2013 21:11:40 +0200 Subject: [PATCH] bcmxcp: Fix method name outputted in debug message, and minor fixes for indentation --- drivers/bcmxcp.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/bcmxcp.c b/drivers/bcmxcp.c index 2e5...

...igned char)0x93 /* Scheduled UPS off in n minutes. length 3-4 */ it is tempting to add support for these as well. But I do not think I have time for that now in the summer. From 0b01612658c1265cb6df8563e0ab7f4d720e8b0f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alf=20H=C3=B8gemark?= <alf at i100.no> Date: Wed, 3 Jul 2013 20:57:58 +0200 Subject: [PATCH] bcmxcp: If UPS supplies command map, use it to control what commands we register with dstate_addcmd. If UPS does not supply command map, we register default commands with dstate_addcmd --- drivers/bcmxcp.c | 39 +++++++++++++++++++...

On Jul 2, 2013, at 5:16 PM, Kjell Claesson wrote: >> I hope other people can also test this. >> >> Regards >> Alf Hogemark > > Due to some crashes on the disks and lack of time I don't have the git on the > pc now. But maybe some other can commit this. I'd like to ask people to specifically try the bcmxcp branch on GitHub - it includes some changes

...do with the ups.load, because I see that there is also code to try to calculate it based on other meter values. I hope other people can also test this. Regards Alf Hogemark From 57a578ad6c4db5c46a41c578b8e8acf098c8ebd2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alf=20H=C3=B8gemark?= <alf at i100.no> Date: Tue, 2 Jul 2013 20:10:37 +0200 Subject: [PATCH] bcmxcp: Add battery.voltage.low and ups.load to meter map, based on info in http://old.networkupstools.org/protocols/eaton/XCP_Meter_Map_021309.pdf --- drivers/bcmxcp.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers...

...s AllocSizeInBits[*] /// ---- ---------- --------------- --------------- /// i1 1 8 8 /// i8 8 8 8 /// i19 19 24 32 /// i32 32 32 32 /// i100 100 104 128 /// i128 128 128 128 /// Float 32 32 32 /// Double 64 64 64 /// X86_FP80 80 80 96 /// /// [*] The alloc size depends on the align...