Recently in the SAS Community Library: SAS' @Sundaresh1 highlights a sometimes overlooked task when applying document embeddings for purposes of similarity-based search. Normalisation of vectors helps obtain relevant matches.
Please correct me if I miss something because just right now the example is a typical example showing how graph can make uses mad.
In the example two formats are used; one is assigned to the variable using the format statement ; the other one is set using the option tickvalueformat.
My original thought was that tickvalueformat would have priority over the variable format to set the tickvalues and that the variable format would be used to set the order of the bars.
However, in this example, we can see that the tick values are coming from the format assigned to the variable, but the format width is coming from the format given in the tickvalueformat option. As the default format label with of the sex format is 6, tick values are truncated.
proc format;
value $sex 'M'='Male'
'F'='Female';
value $sexnum 'M'='1-Male'
'F'='2-Female';
run;
proc sgplot data=sashelp.class noborder;
vbarbasic sex;
xaxis discreteorder=formatted tickvalueformat=$sex.;
format sex $sexnum.;
run;
proc sgplot data=sashelp.class noborder;
vbarbasic sex;
xaxis discreteorder=formatted tickvalueformat=$sex20.;
format sex $sexnum.;
run;
... View more
Sorry for the basic question but I am trying to figure out why data A has only 2 obs while data B has 4. Expecting A to have 4 obs. what is the logic for having only 2 obs ? /* A */
data a;
do i=1 to 4;
i+1;
output;
end;
run;
/* B */
%macro bb;
data b;
%do i=1 %to 4;
i+1;
output;
%end;
run;
%mend bb;
%bb;
... View more
Hi experts,
I am using SAS Mirror Manager and I am noticing something odd. I am using the "--deployment-assets" parameter to point to the deployment assets file downloaded from my.sas.com but it seems like SAS Mirror Manager is always downloading the latest release and not the release found in the deployment assets file.
According to the doc I expected it to download the same cadence and release found in the deployment assets file and not the latest release. I verified the downloaded release in the downloaded path:
../sas_repos/rel/stable/2024.04
I see there:
relFormatVersion":"0.0.1","name":"stable","version":"2024.04","latest":{"duList":"lod/stable/2024.04/20240511.1715441583768
But my deployment assets file name has a different release:
stable_2024.04_20240423.1713898974806
The command I am using is:
$MIRRORMGRPATH/mirrormgr mirror registry --path ${MIRRORPATH} --deployment-data ${ASSETSPATH}/${CERTSFILE} --deployment-assets ${ASSETSPATH}/${ASSETSFILE}
What am I missing here? Maybe I am looking in the wrong place.. where can I see/verify which release was downloaded by mirror manager?
... View more
when use proc logistic procedure to set up default model in bank risk analysis, for the current customer, there are 4 kinds of results after application for the loan, accept, refuse , cancel or nouse. when set up model, to analysis if new customer will default or could approve their application of loan, we will use the current customer loan history. refused=1, accept=0 but how to deal with cancel and nouse, i think nouse looked as accepted, but for cancel, how to deal with it?
... View more