About torestin

torestin · ‎11-21-2019

it took overnight to do a match (400 in products; 2000 pop) and never actually finished it and i had to stop it. Log showed it read both and then nothing. So I am not sure if it actually started execute the hash table. (I am also using the university edition so maybe some restrictions on that?)

torestin · ‎11-21-2019

Hey thanks for that. Yup it works...the only snag is that it seems to get stuck with larger dataset, I was going to do some investigation before coming back.

torestin · ‎11-20-2019

The desired result would look like this: product Customer pay matching result UB LB 137454.2 99272.5 117605 137454.2 99272.5 117605 127407.2 92016.34 120194 127407.2 92016.34 120194 134738.1 97310.83 114285 134738.1 97310.83 114285 118503.5 85585.88 92316 118503.5 85585.88 92316 117691.5 84999.43 125917 117691.5 84999.43 106480 126468.9 91338.66 106480 126468.9 91338.66 125917 138833.3 100268.5 94244 138833.3 100268.5 94244 so that the fifth product is matched with the 6th customer, but the 5th customer (pay) 125917 remains in queue and picks up the 6th product, instead of being skipped altogether

torestin · ‎11-20-2019

right...so this is how i thought hash would work: I need to insert a key/item into both set so they have something to match, and then I see if the condition is satisfied. However, it now says pay is uninitiated so doesn't seem to have read the pay values into the hash table. Where did I go wrong? Data market; input control UB LB; datalines; 1 137454.23 99272.50 1 127407.23 92016.34 1 134738.07 97310.83 1 118503.53 85585.88 1 117691.52 84999.43 1 126468.91 91338.66 1 138833.30 100268.50 ;;;; run; data customers; input control pay; datalines; 1 117605 1 120194 1 114285 1 92316 1 125917 1 106480 1 94244 1 127482 1 94744 1 106371 1 122085 1 100327 1 107315 1 115530 1 116100 1 100279 1 94117 1 111069 1 98615 1 115879 1 124773 1 118694 1 111970 1 118629 1 129623 1 121400 1 100992 1 129743 1 93083 1 90643 ;;;; run; Data M; If _n_=1 then do; Declare Hash m(dataset:"customers"); m.definekey('control'); m.definedata('pay'); m.definedone(); end; Set market; if m.find()=0 then do; If LB<pay<UB then do; Output; m.remove(); end; End; Run;

torestin · ‎11-16-2019

hey thanks for that. 1) actually i am a bit lost about why I put the loop there in the first place now! but it's probably there to enable the leave statement... 2) what I was trying to do was actually to remove both the qualifying range and the customer from the respective sets. So it reads product 1 from the market set, picks out customer 1 from the customer set removes it, then move on to product 2, picks out customer 3, product 3/customer 2, etc. which iterates down the existing queue. I thought the hash table would only give me the match, or non-match - eg if customer 8 cannot find any matching product - but won't do the double elimination?

torestin · ‎11-11-2019

Hi there, i am trying to create a queuing model say something is going to be sold to the first person through the door so long as they satisfy certain income criteria. So it would go something like this a-> person a; b-> person d; e->person b. For each product in list a, it go to the front of the remaining queue and pick the eligible purchaser. My code is pasted below. The issue though is that it seems to move on from ineligible purchasers rather than keeping them in a queue. As you can see below, the 5th customer has too much income for the 5th product, but should have stayed in the queue and takes up the 6th offering. instead, it just skips ahead to the 6th customer. Does anyone know what went wrong and how I can fix it? thanks JC Data market; input UB LB; datalines; 137454.23 99272.50 127407.23 92016.34 134738.07 97310.83 118503.53 85585.88 117691.52 84999.43 126468.91 91338.66 138833.30 100268.50 ;;;; run; data customers; input pay; datalines; 117605 120194 114285 92316 125917 106480 94244 127482 94744 106371 122085 100327 107315 115530 116100 100279 94117 111069 98615 115879 124773 118694 111970 118629 129623 121400 100992 129743 93083 90643 ;;;; run; Data matching; set market; do i = 1 to 7 set customers; if LB<pay<UB And control= . then do; control=1; output; leave; end; end; run; Results: 137454.2 99272.5 1 117605 1 127407.2 92016.34 1 120194 1 134738.1 97310.83 1 114285 1 118503.5 85585.88 1 92316 1 117691.5 84999.43 2 106480 1 126468.9 91338.66 1 94244 1 138833.3 100268.5 1 127482 1

torestin · ‎03-01-2017

It's a bit like the simulated set below 16 obs for this one and the sample set is read 17 times. My own dataset with the front half 0.8*sample_wage<=wage nets the same amount of matches, adding 0.8*sample_wage<=wage<=10*sample_wage nets 5 obs but I can count from the previous matches that there are defnitely more than 5 matches...Any ideas? data Simulated; do i=1 to 100000000; x=ranuni(1); if x < .5 then gender='M'; else gender='F'; y = ranuni (1); if y<.5 then ethnicity = 'B'; if y>.5 then ethnicity = 'W'; if gender='M' and ethnicity = 'W' then wage = 50000+ rand("Normal")*30000; if gender='M' and ethnicity = 'B' then wage = 40000+ rand ("normal")*21000; if gender='F' and ethnicity = 'W' then wage=45000 + rand("Normal")*20000; if gender='F' and ethnicity = 'B' then wage=39000 + rand("Normal")*15000; output; end; run; proc surveyselect data=simulated method=srs n=500 out=SampleSRS (rename=(wage=sample_wage gender=sample_gender ethnicity=sample_ethnicity i=sample_i)); run; data matched; do i=1 to nobs; set samplesrs nobs=nobs; found=0; do j=1 by 1 until (found); set simulated; if sample_wage*0.9<=wage<=sample_wage*10 then do; found=1; output; end; end; end; run;

torestin · ‎03-01-2017

Hi all. Thank you for all your help. I finally put it through the run today and something rather strange happened. For some reason it seems to work with only 1 condition. So it works fine when I tried to match wage lt 1.2*sample wage. Returns 6000 matches. Against 1m records. But adding any other condition returns 5 observations. Doesn't matter if it's another gender ethnicity or or an upper limit on income. Any guess where I went wrong? I struggle to see why adding and wage lt 10*wage sample returns only 5 records or making an ethnicity match..... ##- Please type your reply above this line. Simple formatting, no attachments. -##

torestin · ‎02-25-2017

I thought about that. My question was with that doesn't the inner loop starts from the beginning of the huge set every time? So if the top two in the sample set are m w and the first record of the huge set matches. It will just return that twice. Instead of searching down the list for another match in huge set for no2 on the sample I suppose I could delete the match from the huge set every time. That might work? ##- Please type your reply above this line. Simple formatting, no attachments. -##

torestin · ‎02-24-2017

Hey thanks. Yes exactly. The small data sets will have many obs, so would be very grateful if you or Patrick can suggest how this might be modified. The large set is randomly ordered. Just as a tangent, if a fail safe is needed, would a randomly assigned starting point for the large set do the trick? But anyway, I am starting to think I might have to do random sampling. ##- Please type your reply above this line. Simple formatting, no attachments. -##

torestin · ‎02-24-2017

Hey thanks for that. Sorry I should have been more clearer. What I actually want is for the output to have the same observations with set1 and for each record in set 1 to be matched only once (even if they have multiple matches in set2 on the same criteria). So I changed that to first.id. The first.ethnicity didn't work if I have three lines in set 1 like 232 M W 230 233 F B 240 234 M W 254 etc. as it seems to discard the last record and still returns 2 matches. I tried use first.id (from set2), still doesn't work. Ideas?

torestin · ‎02-24-2017

mmm that still returns two matches for the first line M W in a M W 254 M W 270 F B 234 where as I want it to do M W 254 F B 234 ##- Please type your reply above this line. Simple formatting, no attachments. -##

torestin · ‎02-24-2017

Hi there, I am trying to find a more efficient way to produce a smallish matched control group from a very very very large data set. So what I want is for sas to read 1 record, then find 1 match and then move back to read the next. So say the two data sets look like Data set1; informat gender $1. ethnicity $1.; input serial gender ethnicity wage; datalines; 232 M W 230 233 F B 240 Data set2; informat gender $1. ethnicity $1.; input id gender ethnicity wage; 1 M W 254 2 M W 270 3.M B 255 4 M W 230 5 F B 211 6 F B 222 So the output would be simply 1 M W 254 5 F B 240 I thought about match them first and then trim it down (removing duplicate a.serial). But given the size of the dataset it takes an awfully long time. proc sql; create table control as select a.serial b.* from set1 a, set2 b where a.gender = b.gender And a.ethnicity = b.ethnicity AND a.wage*0.9<=b.wage<=a.wage*1.2 order by id; quit; Any ideas? Thanks

Online Status	Offline
Date Last Visited	‎06-21-2021 10:51 PM

Re: a queueing model

Re: a queueing model

Re: a queueing model

Re: a queueing model

Re: a queueing model

a queueing model

Re: selecting only one match per record

Re: selecting only one match per record

Re: selecting only one match per record

Re: selecting only one match per record

Re: a queueing model

Re: a queueing model

Re: a queueing model

Re: a queueing model

Re: a queueing model

a queueing model

Re: selecting only one match per record

Re: selecting only one match per record

Re: selecting only one match per record

Re: selecting only one match per record

Re: selecting only one match per record

Re: selecting only one match per record

selecting only one match per record