similar to: Asking Favor For "Remove element with Particular Value In Vector"

Dear Prof: My name is Chuan.I from Malaysia.I am a beginner for R.I need favor for Prof. This is my data: y<-c(52,55,61,66,70,61,64,73,63,59,55,90,109,85,69,72,62,59,68,113,144,104,66,73,63,58,71,122,154,106,70,69,67,61,68,104,126,88,68,70,79,65,60,70,77,68,58,75,85,71,64,59,55,61,65,83,87,79,69,68,65,76,78,94) and I form it into matrix as below: [,1] [,2] [,3] [,4] [,5] [,6] [,7] [,8]

Hello,everybody. My name is Chuan Zun Liang. I come from Malaysia. I am just a beginner for R. Kindly to ask favor about median filter. The problem I facing as below: > x<-matrix(sample(1:30,25),5,5) > x [,1] [,2] [,3] [,4] [,5] [1,] 7 8 30 29 13 [2,] 4 6 12 5 9 [3,] 25 3 22 14 24 [4,] 2 15 26 23 19 [5,] 28 18 10 11 20 This

> On Sep 13, 2017, at 9:03 PM, jin chuan see via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi All, > > Thanks for the reply. I managed to identify and fixed a few errors in my implementation. > > However, there are a few errors that i am not sure what is it indicating. > For starters, i think i should explain what i am trying to achieve. > > I am

Running llc with '-verify-machineinstrs' may tell you which instruction break the SSA form. Ruiling From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of jin chuan see via llvm-dev Sent: Monday, September 11, 2017 10:02 AM To: Matthias Braun <mbraun at apple.com> Cc: llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] Live Register Spilling Sorry about the

Hi Matthias, Sorry for the late reply. Yes, you are correct, I do have optnone attribute on my function. I did pass -O0 to the tools. For your information, my invocations are as below: clang --target=mips-unknown-linux -mips32 test.c -emit-llvm -S llc -O0 -march=mips -mcpu=mips32 test.ll -o test.s Based on the generated .ll file, there is optnone attribute on the function, i

Hey Charles, Latest update. Looks like in ups.conf I setup default.input.transfer.low = 84. After I took that line out, restart upsdrvctl, upsmon, and upsd, the command of sudo upsrw -s input.transfer.low=70 -u * -p * ups return OK. Still need to verify if it works by using voltage regulator and will keep you updated. Thank you for your help Regards Shen On Thu, Jun 5, 2014 at 8:54 AM,

Hey Charles, Looks like after take out default.input.transfer.low, upsrw script *DOES* work, the only thing for Eaton 3S 500 is that it is only accept certain voltage values for input.transfer.low, 84v and 96v are two of them. Otherwise the value never gets picked up. Thank you for all your help Shen On Thu, Jun 5, 2014 at 12:07 PM, Shen Chuan <shen at minutekey.com> wrote: > Hey

Hello Charles, Thank you so much for your help. Just run upsc and it is possible that input.transfer.low is the one because we used power regulator to bring down the power around 84v and then the ups sent the power loss message to PC. Do you think some others may take effect for the low voltage? Just have the upsc result attached. Then I retried input.transfer.low, default.input.transfer.low,

Hello Charles, Thank you so much for your reply. Yes. 40v was too low. In windows, those range started from 76v, 85v, and 96v. Just tried upsrw command to modify input.transfer.low and input.transfer.boost.low. There were some error messages returned. Tried another one battery.charge.low and it returns ok. $ sudo upsrw -s input.transfer.low=70 -u * -p * ups Unexpected response from upsd: ERR

Hello Charles, Thank you for your comment. Just tried to use ups.delay.shutdown to postpone the UPS shutdown. The thing is that if the PC shutdown first, then the UPS, it wasn't able to send "shutdown.reboot" any more because everything is power off after the UPS shuts down. Also play on the watchdog for Tripp Lite. Looks like it has the command of reset.watchdog but not

Thanks for reviving this. I completely forgot the details but I resolved this problem. Looking though the code, seems I forked RewriteStatepointsForGC pass, and change it to adding 'gc-livevars' bundle to the call/invoke inst after finding the livevars, instead of changing it to StatepointCall intrinsic. On Wed, Nov 14, 2018 at 11:48 AM Philip Reames <listmail at philipreames.com>

Hi, How to perform a stepwise selection of the best models for gee? Why can't step() do this job? Thanks. Sincerely Yours, Jinn-Yuh Guh, M.D. Dept. of Internal Medicine Kaohsiung Medical College 100 Shi-Chuan 1st Road Kaohsiung, Taiwan FAX: 886-7-312-2810 e-mail: jyuh at mail.nsysu.edu.tw -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Jun 3, 2014, at 5:16 PM, Shen Chuan wrote: > We have an Eaton 3S 550 UPS using NUT tool to send power loss event. By default the power voltage threshold is set to 85 volts. If the voltage is less than 85 volts, it will trigger ONBATT event from NUT. Is there a way in NUT we can change the threshold from 85 volts to a lower voltage like 40 volts? It might be possible with upsrw - try

On Jun 4, 2014, at 6:38 PM, Shen Chuan wrote: > $ sudo upsrw -s battery.charge.low=70 -u * -p * ups > OK Not sure this does what you originally asked, though. Does upsc show any settings related to sensitivity? -- Charles Lepple clepple at gmail

[moving this to nut-upsuser, since other users of Tripp Lite equipment may have specific experience with this.] On Jun 17, 2014, at 7:51 PM, Shen Chuan <shen at minutekey.com> wrote: > We are trying to develop a mechanism to power cycle Tripp Lite UPS. When we checked the upscmd, looks like the only command we can use is shutdown.reboot(sudo upscmd -u user -p password ups

Hello, We have an Eaton 3S 550 UPS using NUT tool to send power loss event. By default the power voltage threshold is set to 85 volts. If the voltage is less than 85 volts, it will trigger ONBATT event from NUT. Is there a way in NUT we can change the threshold from 85 volts to a lower voltage like 40 volts? We were trying to change ups.conf to modify the output of upsc ..., but looks like it

cmpxchg only support exchange on int operands, but pointer values can be very useful here, e.g. stack<T> in a linked-list, the top can be atomic<Node<T>*>. in clang++, cmpxchg operations on atomic<T*> are bitcasted i64 and do the operation, which is ugly. Any reason or concern why cmpxchg doesn't support pointer operands? Thanks -------------- next part

Hi All, I faced some problems while using the BuildMI(). Currently, i am trying to replace specific MI with a series of new MI. I wrote a routine under the processFunctionAfterISel() to detect the targeted MI and replace it accordingly. After using BuildMI() to perform my replacement, i realize there are unnecessary spilling and reloading of registers in the assembly generated. By checking

Hi Team, I'm working on a new pure functional language and I'm trying to add GC support for that. Because all vars are immutable, the IR that my frontend generates are all register based, i.e. no alloca, and no readmem, writemem unless accessing/constructing structs. If I use the traditional GC with gcroot intrinsic, it will need to emit more code for liveness tracking, storing the IR

Hello, We are trying to develop a mechanism to power cycle Tripp Lite UPS. When we checked the upscmd, looks like the only command we can use is shutdown.reboot(sudo upscmd -u user -p password ups shutdown.reboot). Because the PC is connected to UPS directly and we would prefer shutdown PC before power cycle the UPS. But if we run shutdown PC first it won't run the power cycle the UPS script