@Agha wrote: I should calculate the distance between home addresses and closest eye clinic. The addresses are saved in excel. Street, city and state have separate columns. I know I should add double quotation to each part of  the addresses and then find the distance. Can you please share the codes with me. I can not share the addresses with you but they are similar the list below. Thanks.   Street                       state           City aaa bbb ccc             DD             mnv aa dddd eee            DD              dvu ffff oo nnm              DD             lmn   When it comes to long drives or even just routine trips, knowing your car's condition is essential for a smooth journey. I’ve learned the hard way how a small issue can turn a trip into a huge headache. One thing I always make sure to do before heading out is check my car’s history to avoid any nasty surprises, like hidden mileage discrepancies. A great tool for this is https://www.faxvin.com/vin-check/mileage, which lets you easily verify a vehicle’s mileage and overall history by just using the VIN. It’s super handy if you're buying a used car or just want to make sure your own vehicle is up to scratch before a long drive. Trust me, knowing these details makes all the difference when you're on the road! Replace 'your_addresses.xlsx' with the path to your actual Excel file, and ensure the clinic's latitude and longitude are correctly entered. ... View more

Thanks.   Forgot to say I had actually figured this a few days after posting when I realized the code file looks like, well, code. Unfortunately, it's not quite so clear if this is mathematically the same naive Bayes algorithm as GaussianNB in Python (scikit-learn) or naiveBayes in R (e1071), which are what I'm using for class. Doesn't look like I'll be able to use this, but it was a good learning experience at least. ... View more

Thanks for answering. I want it the other way around. From disk to content. Your code does this from content to disk. ... View more

If there are multiple paths from an owner id to a company id, how many observations do you want in the output dataset? One obs, or one obs per path? And if the latter, do you also want measures of the "length" of each path? There are, of course, other possibilities if you have other info available, such as total shares of each company being publicly traded. ... View more

Frustrating and confusing that there are certain procedures included in PC SAS 9.4 m7 that do not function in that environment.  Regardless of whether one uses our own data or not.  When one tries them out the error message is received:   ERROR: The data set SASHELP.CLASS must use a CAS engine libref. NOTE: The SAS System stopped processing this step because of errors.   Agree that PROC GAMPL looks promising.   ... View more

There might indeed be a problem here. (??)   To be sure , can you make your ROC curve again using this technique? Create ROC curve for any predictive model - SAS Support Communities for more info , see : Create and compare ROC curves for any predictive model - The DO Loop   Take (from your Model Studio project) the dataset that contains target and prediction. Then do a PROC LOGISTIC with ROC statement. Your target should be the dependent variable and your prediction (predicted probability) should be the -- only -- independent variable (explanatory variable).   Then compare ...   BR, Koen ... View more

Hi @Taliah  I think this is probably what you are confused about: If you look at the regression model with AR error process discussed in PROC AUTOREG documentation:   SAS Help Center: Autoregressive Error Model   you can see that there is a negative sign in front of the AR parameter φ1 in PROC AUTOREG specification, if you write the complete model with AR(1) error:   yt=xt′β+νt νt=ϵt−φ1*νt−1   since vt-1 = yt-1 - xt-1*β, this implies that    yt = xt*β - φ1*(y_t-1 - x_t-1*β) + ϵt        (1)     Note the negative sign in front of φ1 in the above equation. This has opposite sign for the AR parameter than that specified in the usual ARIMA model expression, as in PROC ARIMA:                                   yt = xt′β +   ϵt/ϕ(B) ,    where ϕ(B)=1−ϕ1B for AR(1) case.   If you multiply both sides of the above equation by (1−ϕ1B), then you get the following:   yt - ϕ1*y_t-1  = xt′β - ϕ1*x_t-1*β + ϵt    this implies   yt = ϕ1*y_t-1  +  xt′β - ϕ1*x_t-1*β + ϵt        (2)   If you compare (1) and (2), you can see that the two specifications have opposite signs on the AR parameter ϕ1.    I hope this helps.         ... View more

As other said why not use the default F-test of PROC GLM ? Although it was almost likely useless due to always yield p-value <0.05 . If you want to compare full-model and sub-model, I would recommend to use likelihood ratio test ,Check @Rick_SAS blog: https://blogs.sas.com/content/iml/2024/03/27/likelihood-ratio-test.html ... View more

Hello ,   See blog on Job flows (in SAS Viya 3.5) : https://communities.sas.com/t5/SAS-Communities-Library/Go-with-the-Job-Flow-in-SAS-Viya-3-5/ta-p/612925   If you have a job (in the flow) that is successful ... the return code = 0. If you have a job (in the flow) that contains a WARNING in the LOG ... the return code = 5710. You can specify (in the job dependencies) that the flow should continue in case of an exit code 5710. I wouldn't put "Ends with any exit code" (!) as event type on the connection ... because then the flow will also continue if the node fails with an ERROR. And in general ... you want the flow to go into abend (you want the flow to stop) if there’s an ERROR. A WARNING is not necessarily an obstacle, but an ERROR is.   The problem is when the node is sometimes returning 0 and sometimes 5710 , because you cannot specify 2 exit codes. (you have this f.e. when you are in the WARNING period with your license key). You can solve that with an OR-gate I believe. An OR-gate is if any of the inputs into it are successful, then the flow will continue, so if you can set the return codes as separate inputs into it, then that should work. The other option is to force the job (node) to return code 0 in the event of a warning. That way, anything other than a successful completion or a warning, stops the job flow. You can use this piece of code for it (to be used with caution ... use it well thought out!): %PUT &=syscc; /* SYSCC Automatic Macro Variable Contains the current condition code that SAS returns to your operating environment (the operating environment condition code). Behavior depends on ERRORCHECK=SAS system option. */ %IF &SYSCC.=4 %THEN %DO; %LET SYSCC=0; %END; %PUT &=syscc; The page you specify for the ERROR-codes is a good one : https://developer.sas.com/rest-apis/compute/docs/error-codes   BR, Koen ... View more

THANK YOU!!!!!! ... View more

Hi Koen(@sbxkoenk),   Thanks so much for your reply!   1) I've tried what you suggested. I've gotten to the point of removing the rows with the 0's that I don't want to display. I'm having some issues formatting the proc tabulate statement to display the outputted dataset from the first proc tabulate. Do you have any guidance on this?   2) Worked perfectly!   Thanks again! ... View more

See above message (also written by me).   I am coming back to this , because the information given (in August 2022) is wrong. You can indeed use the "Manage Variables"-node in a Model Studio VDMML project to make changes to the metadata (role, measurement level, order, ...) of the variables involved, but for the target variable you cannot. For the target variable, the modification screen is greyed out (locked).   In fact, you should also be aware of the fact that the target variable role in a Model Studio project cannot be modified after executing any node or pipeline in it. So, think carefully before defining the target variable in the data pane, because once you start working with it you can't go back!   BR, Koen ... View more