Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - sociallender

Pages: [1] 2 3 ... 19
1
Unfortunately, Dropbox has made a system update recently that has disabled sharing of files (URLs of the past no longer work  because of different address).  This has disabled the ability to automatically update PLS (as well as a couple of other verification checks).  Fortunately, there has not been any updates to PLS recently and you are likely on the latest version.  You can always download the latest from peerlendingserver.com if not. 

BTW, I have been working on a newer system with the help of another benevolent user to create the next release.  We are doing this in our spare time and will likely take a while to finish.  We will let everyone know when the next version is to be released.

SL

2
Peer Lending Server / Re: Finding Null Values
« on: September 21, 2016, 01:58:42 PM »
Close, but NAs are used for missing values.  Here is the code:

is.na(mthsSinceLastDelinq)

HTH, SL

3
Peer Lending Server / Re: Invalid API Response
« on: July 28, 2016, 03:10:14 PM »
Ugghhhh.. I am not sure what is going with LC APIs at the moment.  Usually they fix their issues within a day or so but this has been going on for some time now.  I will be able to dig deeper hopefully tonight (I have not had any free time to investigate).

4
Peer Lending Server / Re: Invalid API Response
« on: June 13, 2016, 05:17:58 PM »
Hmmm... Do you know how many notes were listed with each batch on fractional?  I am not logging that with PLS at the moment.  Were there more than 15 new notes per list?  Looks like ~165K could be less than that number given max amount of 35K per note.  PLS needs 15 notes per list for list detection at the moment.  I don't have the time right now to troubleshoot with code unfortunately.

5
Peer Lending Server / Re: Invalid API Response
« on: June 13, 2016, 04:21:20 PM »
Thanks, I am seeing the same results on my end. 

Now that I am thinking about what is happening, it is likely that LC is sending no data in its API results when no new loans are listed.  This results in an invalid API but I should probably label it differently.  When coding it, I did not anticipate no data meaning no new loans...  However, there are many times where the API payload is empty but there are new loans (I believe it happens when old loans are flushed out of API and new have not been listed).  I will probably put an "empty payload" or something on the status versus API error...

Yes, what is the deal with no new loans?  I am getting cash drag now and not good....

SL


6
Peer Lending Server / Re: Invalid API Response
« on: June 13, 2016, 12:07:12 AM »
Sorry for the delay in responding, I have been traveling this past week.  I am just now taking a look and looks like I am having the same problem.  I noticed that other folks on LA forums are saying that there hasn't been any new notes listed recently?.?.  This would cause the issue of PLS reaching the 300 attempts and not detecting new notes list because it has a minimum new note count of 15 threshold (hard coded) which indicates that new notes are listed.  In other words, PLS will continually poll LC until it finds a note count of 15+ new notes (from current note count) which indicates that the new batch is available.  The reason this is in place is that LC continually adds/removes notes and PLS needs a way to know when new notes have been added (can't rely on timing and there is no field via their API that indicates when new notes have been added).  Therefore, an increase of 15 or more notes indicates new list and PLS will start.  Since no notes or a few have been added, new loan list never gets detected. 

As for the API invalid response, PLS does 3 verifications on the payload of the API response:

* Length of JSON string must be greater than 0 (loan data must be present)
* JSON string must contain a valid field.  PLS looks for "pubRec" in header (arbitrarily chosen) to make sure that it contains information relating to loan data (full verification of all fields would take too long)
* Conversion from JSON to table records must complete successfully

In the past, I have seen payload be empty/missing.  Likely that these errors were due to some technical issue on LC side since no code has changed on PLS.  I don't see the invalid API error in most recent run of PLS but rather the issue of no note list detection.

I am also curious as to why other 3rd party software sites have not reported this API issue (on forum).  Anyone reading this use a 3rd party site and seen this behavior?  Do they log/post the API responses to their users or hide technical issues?  I would assume they are experiencing the same problem as we all connect via the same API.

I will keep an eye on this issue tomorrow and post any new findings. 

SL


7
Peer Lending Server / Re: Invalid API Response
« on: March 09, 2016, 09:33:14 PM »
Thanks for sharing.  Hopefully LC fixes it soon :o

8
Peer Lending Server / Re: Invalid API Response
« on: March 09, 2016, 08:24:33 PM »
Thanks for the heads up.  I am not sure what is going on.  It looks like LC API is not sending back a valid API response. I just ran a quick test of their API manually and the payload is empty:

[1] "{\"asOfDate\":\"2016-03-09T17:12:33.794-08:00\"}"
[1] "{\"asOfDate\":\"2016-03-09T17:12:34.898-08:00\"}"
[1] "{\"asOfDate\":\"2016-03-09T17:12:36.114-08:00\"}"
[1] "{\"asOfDate\":\"2016-03-09T17:12:36.832-08:00\"}"
[1] "{\"asOfDate\":\"2016-03-09T17:12:37.915-08:00\"}"
[1] "{\"asOfDate\":\"2016-03-09T17:12:38.874-08:00\"}"
[1] "{\"asOfDate\":\"2016-03-09T17:12:39.835-08:00\"}"
[1] "{\"asOfDate\":\"2016-03-09T17:12:40.873-08:00\"}"

Each of the above JSON API responses should have loan data included in the response.  PLS does basic data integrity checks to make sure the API response is valid.  Obviously, the response doesn't contain any loan data so it flags as an invalid response.  I am not sure when it started but hopefully LC resolves.  Unfortunately, I am traveling at the moment and can't have a deeper look.   

9
Peer Lending Server / Re: Historical Data
« on: March 09, 2016, 08:19:34 PM »
Thanks for the feedback.  I am working on an updated version in my free time.  It will have updated historical data. The new version should have a single loan historical browser where it will show the ROI calculations.  There are more features that will be included as well but hard to find the time recently. 

I will also try to add a check box for the inclusion of NA for all fields.  May take some time but it will give a bit more control.  In the meantime, you could always create a filter manually.  An older version of PLS had this feature but never added it to PLS 7.  PLS 7 was a complete re-write so I had to determine what were the most important features.

Thanks again for the feedback and will keep everyone posted when I can get a new release out for testing.

10
Peer Lending Server / Re: setting distribution by grades
« on: February 10, 2016, 09:57:03 AM »
Unfortunately, the current version of PLS does not provide distribution allocation.  I am currently working on an update for PLS.  I will look into adding allocation by grade.  Will keep you posted...

11
Peer Lending Server / Re: Model score
« on: January 21, 2016, 06:12:49 PM »
The model is actually an ensemble/combination of many decision trees (google gradient boosted models).  I will be updating the model hopefully soon when I can find the time.  I will create a blog post that will provide more details on how the model is implemented.

The order:

Login
API gets loans
Filter loans using your filter
If # filtered notes > max percent, cancel order
If # filtered notes > max notes per order, only order notes within max notes per order sorted by field (default intRate)

The amount invested per note is what is set in user settings.

Hope this helps. 

Sorry for late response, been traveling...

12
Peer Lending Server / Re: Model score
« on: January 15, 2016, 10:51:36 AM »
The "Social Lender" and "Balanced ROI" are just templates that you can use to set the note selection parameters.  If you click one of these it resets your filter and assigns the predefined filters for that selection.  You can see your parameters at the bottom of the bottom of the summary page.  For example, here are the parameters set for "Social Lender":

model >= 85 & inqLast6Mths <= 2 & installmentIncomeRatio <= 15 & delinq2Yrs <= 0 & pubRec <= 0 & intRate >= 14 & grade %in% c("B", "C", "D", "E")

Now, if you go to these parameters on the left you will see that they are set and you can change them for your particular note selection criteria.  Again, this is just a quick way of setting the filter if you have absolutely no idea of what parameters you want.  I recommend adjusting to suit your needs.

Since this filter has "model >= 85" as part of the selection filter, it will select only notes that have a model score above or equal to 85.  PLS assigns a probability score to each note that predicts the likelihood of the note to be fully paid.  The higher the score, the more likely the model believes the note will be paid.  Of course you dont have to use the model in your note selection criteria.  It is there to help but not required.

When I have time I will be creating a document that details the model  and the process of how it was built.  Its a gradient boosted model which uses an ensemble of decision trees. 

If you want more notes to be purchased, you will need to loosen your filter selection.  I am not sure what your filter looks like but it seems to be selective and perhaps a bit too tight.  Play with your parameters and review the summary page to see historically what percentage of notes match your criteria. 

Maximum notes per order is the max number of notes that can be placed per order.  It is a safety measure to ensure that if your filter is not set correct or too loose you don't buy too many notes.

The max percent is another saftey measure (probably a bit too paranoid) that will cancel the order if it is above the max percent of total notes.  So, if you have it set to 50% and there are 100 total notes that can be ordered, and your filter wants to order 50 or more, the order will be cancelled.  I tried to code in safety measures especially for people who don't understand how to use the software.  I have heard of other tools completely buying all available notes because of a bad filter and wanted to avoid this potential problem.

SL














13
Peer Lending Server / Re: Multiple Accounts Possible?
« on: January 12, 2016, 04:27:57 PM »
Glad you like PLS.  Yes, you can run multiple instances of PLS within VB.  Keep in mind that both instances will poll LC at the same standard times.  If you run too many instances, LC won't be happy about the additional load on their servers.  I haven't heard of any complaints from LC regarding 2 instances running at the same time.  Although I have heard of 3rd party sites that have got in trouble for too much load in the past...

Unfortunately, PLS does not have the ability to run multiple accounts in the same instance.  So, running multiple instances with different users is the only option for multiple accounts.

-SL

14
Peer Lending Server / Re: List detection and then stops?
« on: January 05, 2016, 01:22:07 PM »
Great!  Glad it is working for you. 

Best, SL

15
Peer Lending Server / Re: List detection and then stops?
« on: January 04, 2016, 07:01:31 PM »
Hmmmm... This wasn't what I was expecting.  If it works manually, it should work as a scheduled service.  Can you please try to gracefully restart PLS:

Click the up arrow on the right side of the bottom control panel
Click Shutdown PLS
Then start PLS in VirtualBox.

I haven't heard of anyone else experiencing this issue (I am not as well) so I want to have a fresh start of the OS just in case there is a hung process or something of that sort.  Please let me know how that goes on the next scheduled run.  Thanks.

Pages: [1] 2 3 ... 19